Okay, I put it to different (less restrictive) folder, and it worked.
I also noticed another benefit for using this.
Right now my Kings Of Israel is loading over 100 big sized pictures with
@BRUSH command. When i use Windows IDE and click Run the current script, it takes quite long for it to start running as it adds each picture there or something.
When i either compile with Hollywood itself, or with APPBuilder, It compiles it in 1 second, compared to "run the current script"s 10 seconds. With windows IDE it is too much trouble compiling the script, as i first need to choose compile from left mouse menu, and on top of that choose the versions i wish to build and destination.
But with APPBuilder, I could leave it on background, and everytime i wish to test run the program, i could click the save button, and then build button, and i would get exe in 1 second, then click the exe button, and already be running the program, which is actually faster than using "run the current script" option.
Right now the 10 seconds is still waitable time, although annoying, and not long enough to start complicating life with things like that, but bit more, and need for finding some mean bug which makes you need restarting, and using APPbuilder becomes a viable option for doing it instead of "run the current script".
However, a feature request, or three even, but third one might be too hard to be worth it.
1. Possiblity to choose where the exe will be created at. Right now it creates its own folder with time stamp, which is very nice by the way and useful in some cases too. However, if for example thinking of replacing "run the current script", it would be annoying that while exe would come with click of a button, i would still need to find the exe every time to start it, which would spoil the idea of it being easier with APPBuilder.
Not to mention that for example right now Kings Of Israel takes 50 Mb of size, since i havent altered the pictures smaller yet, hence testing it 20 times, means i have already lost 1 Gb of my harddisk space, unless i take the effort to delete the previous ones, as each compile creates a new folder with new timestamp name, and each takes 50 Mb, supposing i compile for one platform only of course.
Also, I would like to keep the APPBuilder in same folder as my Hollywood, to keep harddisk well organised, but right now due to windws restrictions, i have to move APPBuilder to some other less restricted folder to use it. This problem would get solved by having posiblity to choose where the exe (or folder) is being created to.
2. Having possibility to use the automatic time stamping folder naming, but so that it would always leave only the last compile stay, that the previous compilation folder would always be destroyed,
3. As mentioned, using APPBuilder instead of "run the current script", means i first need to click "save" - button on Windows IDE to save the HWS file, which "Build"-button would then use for compiling. Well, it would be great for it to be able to just compile the current, even if not saved, script to save that one click. Or even better, have "Build" button integrated into Windows IDE version. Just keep APPBuidler open on background and click "Build" in Windows IDE, and it would take all the settings from APPBuilder that is on background open there and make the exe. Then i would just click on that exe (which would always coem to same place) and it be much faster than using "run the current script".