CannotResolveSymbol said:kettch wrote:I could be wrong, but I thought I saw something in a video, or a post somewhere on c9 that talked about MDI in Ava...WPF. The gist that I could see was that when they looked at how various developers were implementing MDI, they saw huge number of variations. Everybody has their own way of doing MDI. So rather than lock everybody into whatever it was that they could come up with, they were going to hold off until a future version until they could come up with a more flexible framework for building MDI apps.
Again, I could be wrong. I really wish I could remember where I saw that...
*wanders off looking bemused*
Nick Kramer's blog: "We don't plan to have a native Avalon implementation of MDI in version 1, mainly because MDI is so easy to do using Windows Forms and Windows Forms interop."
[edit] http://laurenlavoie.com/avalon/80: So there's the other one!! I thought I remembered a second with more detail...
I've run into yet another issue with using WinForms MDI to host WPF content where child forms render incorrectly in a way that introduces visual artifacts when a child form is moved over top another quickly.
How to avoid visual artifacts when hosting WPF user controls within a WinForms MDI app?
http://stackoverflow.com/users/83658/jpierson
I think this is just one more example of how the statement that WinForms already has MDI that can be used through interop is totally bogus and anybody who spend time actually pursuing this route would quickly understand that this isn't an acceptable solution. Unfortunately after evaluating other third party controls such as Actipro's MDI & Docking it also appears that they all have their issues when hosting WinForms content again due to common "air space" issues. I think these are just all great reasons why it would make sense for Microsoft to introduce a WPF based MDI solution and do it right so that introp just works and at the same time fixing the issues with the WinForms MDI interop scenario would help those who need to go down this route for other reasons.