Note: This is an archived post that was originally sent to the Hollywood mailing list on Tue, 23 Jun 2009 17:07:30 +0200
Hello,
Another idea for your todo list When you compile a program in another directory, you use the ASL requester to change the directory and select where you want to store the binary. Then if you want to compile another program, the ASL requester opens in the last opened directory. And you have to browse back to the Hollywood/Examples directory.
Could you separate memorise separately the source and destination directories?
Note: This is an archived post that was originally sent to the Hollywood mailing list on Wed, 24 Jun 2009 11:24:19 +0200
Hello,
Another idea for your todo list When you compile a program in another directory, you use the ASL requester to change the directory and select where you want to store the binary. Then if you want to compile another program, the ASL requester opens in the last opened directory. And you have to browse back to the Hollywood/Examples directory.
Could you separate memorise separately the source and destination directories?
Could be done. Hollywood Designer already does this wonderfully... it even keeps track of all the different requester paths (brush path, picture path, sound path, etc etc.). The reason why the Hollywood GUI doesn't do this is mainly that this GUI was thrown together rather quickly and I think it is never used as often as Designer. So I thought it is ok for the GUI to be a little bit less user-friendly
When you compile a program in another directory, you use the ASL requester to change the directory and select where you want to store the binary. Then if you want to compile another program, the ASL requester opens in the last opened directory. And you have to browse back to the Hollywood/Examples directory.