I'm just starting with the XamDockManager, so hopefully I'm not asking the obvious here. Is there any way to "lock" the layout? For example, let's say the user has the layout just like he wants, and wants to make sure he doesn't move things around by mistake (so easy to do... - e.g. double-click a title bar by mistake and suddenly the pane is floatong.) Essentially I'd like to be able to prevent people from moving/docking/whatever the panes - lock them all in place, but also I want the option of letting them revert to the normal behaviour of the dock manager (a setting would allow them to lock/unlock at will.)
Thanks,Michel
The FlyIn/Out commands are not used to initiate the flyin/out process so the event is not raised. The commands were only added as a convenience to provide a way to programatically show/hide the flyout. That being said, you can report the issue to the support group and we can see if we can raise those events when shown/hidden by the XamDockManager itself.
I hooked a handler to ExecutingCommand on ContentPane, but could not get hit for flyin and flyout command.
I've submitted a feature request for this as well. The xamDockManager is a great way to quickly layout an application, but I would like all user ability to rearrange it removed and there is no easy way to do this. A single property on xamDockManager that removed all the UI for interactive layout (context menus, icons in headers etc.) would be great.
Andrew Smith"]The Window Position menu's visibility isn't currently tied to the presence of items - actually the items are generated on the fly and we raise an event (OptionsMenuOpening) so you could add items to it before its dropped down so I'm not sure we could automatically hide it. We could probably add a property in a future version that we use to bind that element's visibility to provide a way to turn it off without retemplating.
The Window Position menu's visibility isn't currently tied to the presence of items - actually the items are generated on the fly and we raise an event (OptionsMenuOpening) so you could add items to it before its dropped down so I'm not sure we could automatically hide it. We could probably add a property in a future version that we use to bind that element's visibility to provide a way to turn it off without retemplating.
OK, that explains it. I don't think it's much of a big deal, but I'll find out soon enough when I show off the prototype. :)
With regards to dragging within its split pane, cancelling the PaneDragStarting should have prevented any dragging whatsoever (except moving the floating windows). If you're cancelling that event and are still able to move the panes then I would report that to the support group.
Sorry, that was my mistake - I completely forgot to handle that event - it works as expected if I handle it and cancel. I now have the functionality implemented for locking/unlocking the layout and it works great (well, with the limited testing I've put it through anyway. :))
Thanks for your help!Michel