Posted 14 years ago by Steve Weller
Avatar
Hi,
I have just had UIStudio lock up when moving a window to dock as a tab on a floating toolwindow. The "guides" on screen appear as normal windows titled "DockGuideForm" rather than their normal appearance.
Stack trace if breaking in looks like this:
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.UpdateFocusedControl() + 0x30a bytes    
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.AssignActiveControlInternal(System.Windows.Forms.Control value = {ActiproSoftware.UIStudio.TabStrip.TabStripPage}) + 0x26 bytes    
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.ActivateControlInternal(System.Windows.Forms.Control control = {ActiproSoftware.UIStudio.TabStrip.TabStripPage}, bool originator = false) + 0xf0 bytes    
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.ActivateControlInternal(System.Windows.Forms.Control control = {ActiproSoftware.UIStudio.Dock.ToolWindow}, bool originator = true) + 0xac bytes    
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.ActivateControlInternal(System.Windows.Forms.Control control = {ActiproSoftware.UIStudio.Dock.ToolWindow}) + 0x13 bytes    
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.WmSetFocus(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x111 bytes    
     system.windows.forms.dll!System.Windows.Forms.ContainerControl.WndProc(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x25 bytes    
     system.windows.forms.dll!ControlNativeWindow.OnMessage(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x13 bytes    
     system.windows.forms.dll!ControlNativeWindow.WndProc(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0xda bytes    
     system.windows.forms.dll!System.Windows.Forms.NativeWindow.Callback(int hWnd = 1117490, int msg = 7, int wparam = 5507536, int lparam = 0) + 0x4a bytes    
     system.windows.forms.dll!System.Windows.Forms.Control.FocusInternal() + 0x4c bytes    
     system.windows.forms.dll!System.Windows.Forms.Control.Focus() + 0x2d bytes    
     actiprosoftware.uistudio.dock.dll!ActiproSoftware.UIStudio.Dock.ToolWindow.Activate() + 0x176 bytes    
     actiprosoftware.uistudio.dock.dll!ActiproSoftware.UIStudio.Dock.DockManager.ᐅ(bool  = false) + 0x61c bytes    
     actiprosoftware.uistudio.dock.dll!ActiproSoftware.UIStudio.Dock.DockManager.ᐘ() + 0x11 bytes    
     actiprosoftware.uistudio.dock.dll!ActiproSoftware.UIStudio.Dock.DockManager.ᐆ(System.Object  = {ActiproSoftware.UIStudio.Dock.ToolWindowContainer}, System.Windows.Forms.MouseEventArgs  = {X=653 Y=371 Button=Left}) + 0x29 bytes    
     system.windows.forms.dll!System.Windows.Forms.Control.OnMouseUp(System.Windows.Forms.MouseEventArgs e = {X=653 Y=371 Button=Left}) + 0x5b bytes    
     actiprosoftware.winuicore.dll!ActiproSoftware.WinUICore.UIControl.OnMouseUp(System.Windows.Forms.MouseEventArgs e = {X=653 Y=371 Button=Left}) + 0x14b bytes    
     system.windows.forms.dll!System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message m = {System.Windows.Forms.Message}, System.Windows.Forms.MouseButtons button = Left, int clicks = 1) + 0x261 bytes    
     system.windows.forms.dll!System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x49b bytes    
     system.windows.forms.dll!System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x6c bytes    
     system.windows.forms.dll!ControlNativeWindow.OnMessage(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0x13 bytes    
     system.windows.forms.dll!ControlNativeWindow.WndProc(System.Windows.Forms.Message m = {System.Windows.Forms.Message}) + 0xda bytes    
     system.windows.forms.dll!System.Windows.Forms.NativeWindow.Callback(int hWnd = 4459176, int msg = 514, int wparam = 0, int lparam = 24314509) + 0x4a bytes    
     system.windows.forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop(int dwComponentID = 7, int reason = -1, int pvLoopData = 0) + 0x349 bytes    
     system.windows.forms.dll!ThreadContext.RunMessageLoopInner(int reason = -1, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.ApplicationContext}) + 0x1f3 bytes    
     system.windows.forms.dll!ThreadContext.RunMessageLoop(int reason = -1, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.ApplicationContext}) + 0x50 bytes    
     system.windows.forms.dll!System.Windows.Forms.Application.Run(System.Windows.Forms.Form mainForm = {Collins.Datalink.SkyView.MainForm}) + 0x34 bytes    
>    SkyView.exe!Collins.Datalink.SkyView.AppController.Main() Line 305

Comments (9)

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Can you give exact steps to duplicate it in the sample project? I can't repro it here so far.


Actipro Software Support

Posted 14 years ago by Steve Weller
Avatar
Can reproduce (hard without screenshots though):

Run sample app.
Drag and Float "Tool Window Properties"
Drag "Dock Manager Properties" tab inside "Tool Window Properties" so it is docked beside "Tool Window Properties". i.e. two tabs are now side by side in an untitled window.
Press Auto-Hide for "Tool Window Properties" - auto-hides on main app frame.
Press Auto-Hide button again for "Tool Window Properties" - docks to main app frame.
Drag "Tool Window Properties" and attempt to dock as tab within floating window ("Dock Manager Properties")
Boom!
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
I'm still not able to dupe any problem. I'll try and have some testers check it out as well.

BTW, you found a bug too. The auto-hide button should not be visible on floating window title bars. :)


Actipro Software Support

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
I had two other customers try to duplicate it and they have been unable to cause it to break either. Are you able to duplicate it another way since the next build will no longer have auto-hide buttons in the floating windows anyhow.


Actipro Software Support

Posted 14 years ago by Steve Weller
Avatar
Havent seen it happen any other way. I mailed in screenshots with each step - has anyone tried to reproduce the problem using those?
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Actually I was doing the same things as in your screenshots based on your original posting. Anyhow, like I said, that functionality is no longer available after the next build since it never should have been there.


Actipro Software Support

Posted 14 years ago by Steve Weller
Avatar
The behaviour did seem weird, so that's fine.
Can you give me any idea on a ship date for a fix?
We are nearing a release for our software and this seems like quite a serious bug since it takes 100% CPU
as well as rendering the app useless...
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
I would think in the next week or so. We've seen a couple cases where Microsoft's code goes into infinite loops now. Although this is one we haven't run into before. Another one is one with SelectNextControl which can lock up an application and we've had to work around that bug. What .NET framework do you run by the way?


Actipro Software Support

Posted 14 years ago by Steve Weller
Avatar
We're using version 1.1
The latest build of this product (v2018.1 build 0341) was released 9 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.