Hey Ryan.
From what i understand, "OnPopUpClose" is more of a notification to the parent screen that its child screen is now closed.
Actions used during "OnPopUpClose" only have access to fields from the parent screen, which gave me a limitation i wasn't sure how to work with. OnScreenClose would have been running actions with access to the current active screen just before closing it, irregardless of whether that screen was a parent, child, or lone screen.
At this point, i believe i have found a work-around to accomplish what i was trying to do. It'll just be a little less clean-cut.
----------
One of the other reasons i push this particular Event is due to the ability to guard the user from silly mistakes such as accidently closing the screen and losing settings or data. I'd like to be able to employ, on a screen, the same warning system we see in every-day applications -- [ You have chosen to close without saving your data, are you sure? (Y / N) ].
Or [Your settings from this session are about to be saved, is that okay? (Y / N)] .. etc etc. Method's customization is in essence a watered down version of a windows application with controlled limitations.The more control we have on how a screen functions with our users, the safer and more efficient it will be to use.
Let me know your thoughts,
Thanks,
~Joe