Floating Pane associated with wrong Frame

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I recently updated my current project to use the 13.4.2 version of the toolkit instead of version 12, and now we have a problem. We have two main windows in our application, both of which are docking sites. When a pane is undocked, it normally stays visible in front of the frame it is associated with (you can't hide it behind the docking site window). As of the library upgrade, however, all floating panes seem to have this association with the application main frame window, not their docking site. Has anybody else seen this?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
acwest Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 23 April 2010 Location: Canada Status: Offline Points: 16	Post Options Post Reply Quote acwest Report Post Thanks(0) Quote Reply Topic: Floating Pane associated with wrong Frame Posted: 04 November 2010 at 3:35pm
	I recently updated my current project to use the 13.4.2 version of the toolkit instead of version 12, and now we have a problem. We have two main windows in our application, both of which are docking sites. When a pane is undocked, it normally stays visible in front of the frame it is associated with (you can't hide it behind the docking site window). As of the library upgrade, however, all floating panes seem to have this association with the application main frame window, not their docking site. Has anybody else seen this?

acwest Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 23 April 2010 Location: Canada Status: Offline Points: 16	Post Options Post Reply Quote acwest Report Post Thanks(0) Quote Reply Posted: 11 January 2011 at 4:20pm
	Has NOBODY seen anything like this happen?

acwest Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 23 April 2010 Location: Canada Status: Offline Points: 16	Post Options Post Reply Quote acwest Report Post Thanks(0) Quote Reply Posted: 11 January 2011 at 5:20pm
	After some investigation, I have discovered the problem, and I think it is a bug. In CXTPDockingPaneMiniWnd::Create, there is a pair of lines: CWnd* pParentWnd = GetDockingPaneManager()->GetSite(); if (pParentWnd->GetStyle() & WS_CHILD) pParentWnd = AfxGetMainWnd(); The problem is that the docking site is not the top level frame, and the top level frame is not the main window (There are multiple top level frames in the app) This results in incorrect behaviour. I can probably work around it by re-writing the Create method in my subclass of CXTPDockingPaneMiniWnd, but I would prefer a more elegant solution...