There is a catch to it, in that it has a few quirks here and there.. Time Heuer has upgraded it a little via this project - http://floatablewindow.codeplex.com/
I've also written some code to help folks figure out the ChildWindow's location when you go to close it (at times can be useful for persisting windows to emulate a "hibernate" style approach to resuming a UI). http://stackoverflow.com/questions/2707789/how-to-know-the-position-of-the-silverlight-childwindow-when-you-close-it/2729442#2729442 etc.. From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Monday, May 10, 2010 11:16 AM To: 'ozSilverlight' Subject: RE: Simulating modal dialog +1 ChildWindow. I'm using that for login window, change password window, message prompts etc. It's great and even has its own funky animated show/hide. Holy sh*t! The ChildWindow class is fantastic. It dims and blocks the app background and it animates beautifully. I can't believe this control actually works so well with little effort and that it looks so nice. It's a shock on the eyeballs, so I will only use it judiciously in my app where the user's attention is required for something important. In my case I'm adding a global error handler to show a "sorry for the inconvenience" apology when something unexpected happens. Hmmm! Error handling is a whole subject in itself eh! I'd be interested to hear from others on the subject if you have strong opinions or snazzy tricks. Cheers, Greg
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
