BMP Not getting new files

[macroman]

I generated script ABC.exe, it also generated a bmp folder named ABC.... same script, I just decided to name a different .EXE file, which is DEF.exe... it created a folder name DEF with all the BMPS as well... then I continue to work on my scripts also generating new BMPS, it gets stored in ABC folder and not in DEF when exporting, even though I checked the mark to generate it's own BMP folder... Now I have to copy and paste new bmps from the original folder to the new one, very annoying... please help

[Marcus Tettmar]

I don't really follow.

When you create a .exe of your script that is a one time snapshot of the script at that point. You aren't changing how you make your script. Your script is still ABC and is still using the ABC folder. But each time you recompile - which you will need to do if you make changes and want to reflect those changes in your .EXE it will copy everything to the destination folder.

Creating a .EXE is NOT changing the working folder. The working folder remains the same. But it will copy the BMPs to the destination folder.

[macroman]

That's correct.

When I compile to DEF.exe from macro named ABC, it does copy everything over to DEF BMP folder... when I add something new, recompiled to exe DEF, the new BMP files does not get copied over to the DEF, but instead it goes back to the first folder which is ABC....

Keep in mind, I didn't Save the Macro under a new name, I'm just naming my .EXE compiled file differently... my Macro name is still ABC - but I want the exe file to have a different name... the job name is ABC, but when I compiled to EXE, i name it DEF.exe.... everything in folder ABC should be copied over to DEF.... It does, only the first time... when I go and add a new image recognition capture, and recompile the exe, it does not copy/move the new BMP to the DEF folder. This has been going on a few versions now... you can test this or I can do a video for you...

[Marcus Tettmar]

Sounds like it is not overwriting then. Will check this out. In the mean time deleting the DEF folder before compiling should do the job.

[Marcus Tettmar]

I have replicated this and I see now why this happens. It's an inadvertent side affect of a safety feature - we did not want to overwrite any existing folder that may already have been in the target folder with the same name - e.g. you may already have a DEF folder which you would not want overwritten. Of course this means it's not being updated on second compile either. I guess what we need is to "merge" with any preexisting folder instead and/or prompt/warn the user. Will get this sorted!

[macroman]

awesome! Thank you. If I could only remember this bug, I would just copy the new BMP's myself... but there are days you just forget and spent hours trying to figure why it couldn't find the green arrow

[macroman]

Just wasted another 2-3 hours debugging, then i realized it didn't have the new bmps that didn't get copied over. when will you have this update available for download?

[Marcus Tettmar]

It's fixed in dev. So should be soon. But there's a few other things we'd like to get into this update. The summer holiday period has delayed us a little.