Dear Harald,

Thanks for posting your questions in our community forum.

I'll specifically address your concerns about the 2nd and 3rd point.

For point 2), apparently it's not the issue in Grid nor the double-click implementation. The actual issue is that the dialog box doesn't recognize the 2nd window as a valid root visual, thus it displays the dialog in the first (main) window. This is an issue and will be addressed in our upcoming builds.

Also, since you didn't give detailed information about the platform and controls that you're using, I'm assuming that both points are specific to WPF platform, and that the dialog you mentioned is a UXDialogBox, not WPF's native dialog box.

For point 3), please keep in mind that UXWindow and UXDialogBox are framework elements, they are not native WPF windows. The IWindow is introduced for cross-platform support (Silverlight + WPF) and is a core infrastructure for our windowing framework. Our windowing controls are designed to provide a number of rich capabilities not available in standard WPF windows such as desktop-style MDI windows, integration with application launcher control (Dock-style taskbar), and more. You can find out the complete information about our windowing architecture here: http://www.intersoftpt.com/Support/ClientUI/Docs/WindowOverview.html

Now it's clear that our windowing controls aren't WPF windows, you need to consider which windowing control that suit your applications. The simple rule of thumb is that, if you want to display a child window within your window, then choose UXDialogBox. Otherwise, you can just use WPF's native Window and show it as modal. Of course, in this case, you'll see a separate window out of the current window.

In addition to the element-based window controls, we actually had real WPF windows. The first is called UXGlassWindow, allowing you to create modern window with glass visual effect. And the second is UXRibbonWindow which you can use to host a ribbon control in a transparent window that simulates the appearance of Office 2010. Everything is written in our comprehensive documentation if you want to learn further.

Last but not least, the UXWindow/UXDialogBox controls did have WindowStartupLocation property. Simply set it to CenterScreen will make your window/dialog appears in the center. If that doesn't work, then I'll need to ask for the version and build number you're using.

Please feel free to submit the other issues you found. We'll be happy to review if they are really issues, or there are something we can assist.

Best,
Jimmy

Hi Michael,

Thanks for your valuable feedback!

The statement of "no plugins will be allowed in Windows 8" appears to be only partially correct. Windows 8 will continue to support plugins in the Desktop mode. So the "no plugin" context applies only to the Metro mode. This, however, is still in speculation in the current stage. There have been rumors that Microsoft might make their way to exceptionally support Silverlight in Metro mode, although they may have no intentions to support any other plug-ins. This is possible since MS has been making more exceptions on the Metro, for example, Office 15 will exceptionally support Metro eventhough its codebase is originally built for Desktop mode. So let's wait and see their next move.

Best,
Jimmy