Hello, I have. problem, with the new version (the one I had to download for the problem with the new mac's update) when I add more than one photo the program crash. I had to quit end open it again. how can I solve this problem? Thanks.
top of page
bottom of page
My app crashes/freezes when I'm logged into my account and try to sync and quit. When I'm logged out of my account, the app quits without crashing.
This new build (1.60.17) appears to be working for me! Will report back if I encounter more glitches. Thank you.
Please try the 1.60.17 build at https://www.hollywoodcamerawork.com/shot-designer-betas.html
yes it's true, it happens also withe the background images...
I've noticed the same behavior happens when importing background images. The first import works, but the second time I need to import I have to force quit and then re-open the app. Looking forward to the update.
Thx a lot!
I located the issue on the AIR SDK bug tracker. This is a recent regression in the underlying framework, the feature was broken by an Apple update, and they have an updated framework. So expect an update in a day or two.
hi, well didn't work... every time I had to close and open the app again.
Since the issue doesn't happen here, it's more difficult to address. There's a 1.60.16 build you can install now, which is an attempted fix that I need affected users to run.
There are no guarantees. This kind of debugging is based on trying to guess odd ways the code could misbehave.
In this case, the guess is that the a File object is created and then browseForOpen is called on it. At this point, the file selector should take over the garbage collection scope and return the file object with the File Selected event. So the guess is if there's a bug somewhere in their framework and the file object actually loses scope when passed on the file selector and the calling function exits, it could fall out of scope before the selection is complete. So the attempt is to make the file object persistent. But this should crash, not hang, so it doesn't explain it.
Secondly, when the file object is created, an event listener is assigned to it in order to receive the selected file. Let's guess that there's a bug somewhere in the interface to the system file selector, where only one such event listener can be assigned, and we're doing it every time. That could explain hanging on the second attempt, although it doesn't explain why it only happens to a tiny fraction of users. So again, making the file object persistent could resolve it.
You may not understand the above, and that's fine. It's only to say that it's difficult to debug a problem that you can't get to inspect. The code is not wrong. So all you can do is try to think outside the box for ways you might interact poorly with external libraries, or interact poorly with an external bug, or how you might be using the APIs incorrectly.
Please install it and let me know if a second file selection works.
This is happening to a couple of dozen other people. I still don't know what causes it, and it happened at a terrible time, because I'm trying to get from under another project in order to be able to invest the time it takes to understand this problem. But I'm almost out, and then we can have Shot Designer and Green Screener updates.