Is it just me or is there a trouble with a generated engine again.
I can remember a few years (versions) ago that when an engine was created to
drive a stack we got memory leakage (check the windows task manager) when
the app was closed. Simply put the stack closed but the engine stayed in
Cal,
Try this :
on quit
save stack yourstack
wait 1
quit
end quit
Best,
Pierre
Le 9 oct. 2010 à 05:27, Cal Horner a écrit :
Is it just me or is there a trouble with a generated engine again.
I can remember a few years (versions) ago that when an engine was created
-revolution.278305.n4.nabble.com/Engine-Trouble-tp2969331p2969394.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage
Hi Cal,
Your message confused me but after reasing the other answers on this list I
understood what's wrong. What you are describing is not memory leakage. It is
simply a quit command badly executed. This solves the problem:
http://runrev.info/Save%20Way%20to%20a%20Quit.htm
You may need to
On 10/8/10 10:27 PM, Cal Horner wrote:
Is it just me or is there a trouble with a generated engine again.
I can remember a few years (versions) ago that when an engine was created to
drive a stack we got memory leakage (check the windows task manager) when
the app was closed. Simply put the
