DocumentWindow.Activate does not activate window

Docking/MDI for WPF Forum

Posted 8 years ago by Martijn van Kleef - FEI
Version: 11.2.0552
Avatar
Hi, we have DocumentWindows in a TabbedMdiHost container. When adding a DocumentWindow and then calling Activate() on it, the workspace appears to become active but the window is not activated or selected. The last Actipro event I see is PrimaryWindowChanged, but I also expected ActivateWindow followed by LastActiveDocumentChanged. In the PrimaryWindowChanged event I noticed the DockSite.ActiveWindow was set to null and the TabbedMdiHost.PrimaryWindow was set to the window that should have been Activated. It's a long shot but I haven't got anything else to go on anymore and I'm quite stuck, so, please: any clues as to why the call to Activate() failed silently for the DocumentWindow?
PS: our Actipro release is 11.1.0545.

Comments (2)

Posted 8 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Martijn,

Sorry, but it would be impossible to tell without a sample application that reproduces the behavior you are seeing. But keep in mind that the PrimaryWindowChanged event may fire before the DockSite WindowActivated event, if that is what you are referring to.

If you can please put together a small sample project that reproduces your issue and email it over then we can take a closer look. Be sure to remove any executables or change the extension of the zip file to ensure it gets past our email filters.


Actipro Software Support

Posted 8 years ago by Martijn van Kleef - FEI
Avatar
never mind, I created a small project to reproduce but that didn't feature the reported behavior. eventually it turned out a little hidden preview-event-handler ate an event causing the dockingwindow never to get activated.
The latest build of this product (v2019.1 build 0683) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.