David,

>That should be handled by the app help file and end user training.

Let's modify the use case to say: "to provide the benefits of a docked environment and be able to lock or unlock the configuration programmatically once docked"

Another option on the dockable property would support this:
0 - Docking not supported
1 - Participates in docking, but not dockable
2 - Participates in docking, and is dockable
3 - Lock current docking status && new option

Then, switching programmatically between 3 and 4, we could control positioning and layout of forms, but lock the layout (and optionally give certain users the ability to undock).

After all, we now have anchors to dynamically reposition items on a resize, but we don't also give the user the ability to drag the controls all over the page to break the anchored configurations.

>
>>The use case is to provide the benefits of a docked environment without allowing the less-than-power-users to become confused and entangled in how to re-dock it when they mess it up.