Program stack in standalone retains changes after quitting and relaunching application

10 views
Skip to first unread message

Martin Koob

unread,
Feb 12, 2015, 6:30:44 PM2/12/15
to glx...@googlegroups.com
In my program stack after the program has launched I clone graphics and paste them on the car.  Then a cleanup routine deletes them on quitting the application. Also the state of some buttons are set to disabled state in the cleanup routine.

Occasionally in the standalone i encounter an error where the cleanup routine doesn't run and the graphics that were added do not get deleted by script and buttons do not get reset to disabled.

I thought this should not be a problem because I thought the program stack can't be saved as it is in the standalone's bundle.

However the next time the program launches the graphics are still in the stack and the buttons have not been reset.

Is it possible that changes to the program stack are changed in a standalone?


Martin

Trevor DeVore

unread,
Feb 13, 2015, 8:44:57 AM2/13/15
to glx...@googlegroups.com
On Thu, Feb 12, 2015 at 6:30 PM, Martin Koob <in...@videolinkwell.com> wrote:
In my program stack after the program has launched I clone graphics and paste them on the car.  Then a cleanup routine deletes them on quitting the application. Also the state of some buttons are set to disabled state in the cleanup routine.

Occasionally in the standalone i encounter an error where the cleanup routine doesn't run and the graphics that were added do not get deleted by script and buttons do not get reset to disabled.

Only possibility is that an object that you are trying to delete is running a script. For example, if a button calls a handler in your card in mouseUp and the handler in the card tries to delete the button then you will get an error. Any chance this could be the cause?
 
I thought this should not be a problem because I thought the program stack can't be saved as it is in the standalone's bundle.

However the next time the program launches the graphics are still in the stack and the buttons have not been reset.

Is it possible that changes to the program stack are changed in a standalone?

If you are issuing a 'save stack' command then yes. The program stack is not bound to the engine, only the glxappLauncher stack is. All other stacks are just stack files on disk.

-- 
Trevor DeVore
ScreenSteps

Trevor DeVore

unread,
Feb 18, 2015, 8:56:46 AM2/18/15
to glx...@googlegroups.com
On Fri, Feb 13, 2015 at 8:44 AM, Trevor DeVore <glx...@gmail.com> wrote:
Only possibility is that an object that you are trying to delete is running a script. For example, if a button calls a handler in your card in mouseUp and the handler in the card tries to delete the button then you will get an error. Any chance this could be the cause?

"Only" in the sentence above should be "One".
Reply all
Reply to author
Forward
0 new messages