On May 15, 2009, at 1:22 PM, Jim Bufalini wrote:
Does anyone know what could prevent a stack from being removed from
memory
if the destroyStack and destroyWindow of the stack is set to true
and there
is no processing or messaging going on (that I'm aware of) that
would keep
the stack open until processing completes?
The window closes, but the stack remains open in the Application
Browser.
Selecting Close and Remove from memory in the Application Browser
prompts
for an acknowledgement, but after clicking OK the stack remains in
memory
and in the Application Browser.
I seem to see this when I have library stacks in use.
Devin
Devin Asay
Humanities Technology and Research Support Center
Brigham Young University
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
