We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

Floating Window has disappeared, after changing the state to float programmatically.

Hello,
I'm trying to undock tabbed windows by settting the set DockingManager.State property programmatically to DockState.Float.
Once that works well, but after tabbing it by drag and setting the state again to float the window disappears (See attached sample code).

Another problem that sometimes occurs is that the window can't be docked again, because DragProviders aren't displayed.

Are there any ideas why this happens?

Regards,
Elmar

Attachment: HiddenDockingWindowExample_c6e0a5cb.zip

7 Replies

VJ Victory Jessie Selvam D Syncfusion Team June 15, 2016 11:26 AM UTC

Hi Elmar,

Drag providers will be displayed for a floating window only if it is in Dockable state. A floating window can be moved to Dockable state using Dockable option in context menu. We have modified your sample to enable context menu in NativeFloatWindow. In the sample, we have applied default style for NativeFloatWindow by setting BasedOn style, so that context menu is enabled. You can download the sample from following link:

Sample: HiddenDockingWindowExample

We were unable to reproduce the reported issue "After tabbing floating window by drag and setting the state again to float the window disappears" with the modified sample. Could you please check this sample and get back to us with issue replication video if issue still persists? This would help us to proceed further.

Regards,
Jessie


ES Elmar Strittmatter June 15, 2016 12:19 PM UTC

Hi Jessie,

Thank you for the hint with the Dockable state.

The issue "After tabbing floating window by drag and setting the state again to float the window disappears" still persists with the modified sample.
I attached a short replication video. After 0:12 on timeline the window "Page 1" has disappeared?!

I hope you can reproduce it.

Regards,
Elmar

Attachment: disappearing_window_video_708beced.zip


DR Durga Rajan Syncfusion Team June 16, 2016 12:24 PM UTC

Hi Elmar,

We were able to reproduce the reported issue "After tabbing floating window by drag and setting the state again to float the window disappears". The fix for this issue will be available along with Volume 2 which is scheduled to be rolled out by next week.

Regards,
Durga S.


ES Elmar Strittmatter replied to Victory Jessie Selvam D June 16, 2016 02:18 PM UTC

Hi Elmar,

Drag providers will be displayed for a floating window only if it is in Dockable state. A floating window can be moved to Dockable state using Dockable option in context menu. We have modified your sample to enable context menu in NativeFloatWindow. In the sample, we have applied default style for NativeFloatWindow by setting BasedOn style, so that context menu is enabled. You can download the sample from following link:

Sample: HiddenDockingWindowExample

We were unable to reproduce the reported issue "After tabbing floating window by drag and setting the state again to float the window disappears" with the modified sample. Could you please check this sample and get back to us with issue replication video if issue still persists? This would help us to proceed further.

Regards,
Jessie

Hi Jessie,

I tried your sample for " NativeFloatWindow with Dockable option in context menu".
Now, the window looks like with setting UseNativeFloatWindow="False".
Is it possible to get the NativeFloatWindow in Dockable state without "Aero" Style?

Regards,
Elmar


VR Vijayalakshmi Roopkumar Syncfusion Team June 17, 2016 01:21 PM UTC

Hi Elmar,

Thank you for your update.

In our DockingManager control, the difference between the FloatWindow and NativeFloatWindow is that the NativeFloatwindow can able to resize like normal WPF Window. So on overriding the NativeFloatWindow, its functionality remains the same as FloatWindow. UI will not change for NativeFloatWindow and normal FloatWindow.

Please let us know if you have other concerns.

Regards,
Vijayalakshmi V.R.
 



ES Elmar Strittmatter June 17, 2016 02:41 PM UTC

Hi Vijayalakshmi,

in Jessie sample  (HiddenDockingWindowExample), he applied a style for NativeFloatWindow by setting BasedOn style, so that context menu is enabled. This solves my problem that sometimes floating windows can't be docked (caused by that they wasn't in dockable state).

<syncfusion:DockingManager.NativeWindowStyle>

<Style BasedOn="{StaticResource AeroNativeWindowStyle}" TargetType="syncfusion:NativeFloatWindow">

<Setter Property="Background" Value="White"/>

</Style>

</syncfusion:DockingManager.NativeWindowStyle>


This has the ugly side effect that it no longer looks like a normal WPF Window.

Isn't it possible to get the NativeFloatWindow in Dockable state without this side effect.


Regards,

Elmar





VR Vijayalakshmi Roopkumar Syncfusion Team June 20, 2016 12:23 PM UTC

Hi Elmar,

Query#: Is it possible to get the NativeFloatWindow in Dockable state without "Aero" Style? Isn't it possible to get the NativeFloatWindow in Dockable state without this side effect.

When we override the AeroNativeWindowStyle for the NativeFloatWindow, the NativeFloatWindow will look like a normal FloatWindow. It is the behaviour of the DockingManager.

Query#: that sometimes occurs is that the window can't be docked again, because DragProviders aren't displayed.

In our DockingManager we have displayed the DragProviders based on the mouse position of NonClientArea and Dragging of NativeFloatWindow. Due to override the default NativeFloatWindow style, it will affect showing drag providers. But we can get the DragProviders once we mousehover inside the client area or click inside the client area of NativeFloatWindow.

Regards,
Vijayalakshmi V.R.

Loader.
Up arrow icon