I think I tried something like that (my experiments in that direction were several days ago and I didn't get the results I wanted so I kinda lost track of the details during the abandonment... ).
Anyway, as I recall, overriding shutdown(...) only allowed me to veto the "Application is Going Away Now" process. But then I can't ever shut it down (from the inside - thank the Demons of Kill-9 Lane for other options). Perhaps you meant something otherwise, but that was my experience. I suppose I could somehow "get into" the underlying list of Displays who's closing signals Application Termination and modify / intercept / twistify it - but that seems even less clean (even if I don't have to modify any code). What I REALLY meant by "cleaner" and "well integrated" is advice on how to (re)write my modifications to the DesktopApplicationContext class so they are "more betterer." Perhaps some other class altogther? Perhaps a new flag argument to createDisplay(...)? (Why not even one more??) My larger concern is that I'm somehow missing something important in how everthing all fits together and that I'm creating some subtle problem - but unless some Hero of Pivot can help resolve that concern I'll be moving on for now... PS - I can post a diff / patch if peoples are interested, especially one of those Heroes . -- View this message in context: http://apache-pivot-users.399431.n3.nabble.com/How-to-open-two-windows-tp2022668p2646021.html Sent from the Apache Pivot - Users mailing list archive at Nabble.com.
