Hello Gary,
ObjectMemory quit is fine. To close a window politely, you can send closeRequest to an ApplicationModel (which allows it to refuse in changeRequest) or to force closing, send closeAndUnschedule to its controller (or ApplicationModel, which forwards it; ScheduledWindow doesn't implement it, at least not in 7.7.1). Looking at senders of #closeAndUnschedule can give you some hints, e.g. VisualLauncher also sends #release, and CancelableNotice makes sure to do the closing from the UI process. There's some more information about closing windows in a post from a couple of years back (the GDI objects part bit me yesterday in 7.7.1, but has hopefully been fixed in a more recent version):
If you have windows hanging around, try looking at the Reference Path for one from Trippy (you will need the AT System Analysis parcel from the advanced directory). We just had a case the other day in 7.7.1 where the WindowManager of several windows had finished, the windows been closed, its baseProcess terminated and its windows collection empty. However, it still had events in its eventQueue, and thus the terminateIfFinished message did not finish cleaning it up (the comment in that message says it checks if it has no windows, but it actually checks it has no events). The WindowManager remained in the registry, and the events referred to the windows, so they were not gc'd.
All the best,
Steve
Hello All,
Wondering if this is the suggested exit from a RunTime -
ObjectMemory quit
Wondering if this is the suggested close a window/dialog -
window closeAndUnschedule
I ask because we seem to be getting some residue windows in the dev image; so would take any guidance to help look for roots.
Thank you,
Gary P
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
