Replacing old AQDock docking manager with LMD Dock

Intrepid Control Systems Inc

Hello LMD team,

We are replacing an old docking manager with LMD.  So far, everything works as expected.  When we create new windows, I can create them as the dkTool type, and that type ALSO allows docking.  The problem with the dkTool type is that it doesn't seem to support tabbing, so when several items are docked in a dkTool, we will see a button bar along the bottom, which won't replace the AQDock functionality exactly.

To replace AQDock functionality, I would like to have new forms use the ClientKind = dkDocument, which does not allow docking by default.  My thought is that I could add a site to all dkDocument windows.  The dkDocument would then allow tabbed content, which would duplicate what we had with AQDock.  Is this the right way of thinking and do you have any suggestions on how to go about this?

As a side note, I noticed an existing VCL property that was accidentally set on a couple of our forms called DockSite = true -- interestingly, LMD wrapped windows would interact with those windows, although the results were not as expected and I've since removed this propertly.  If it is as simple as setting a property, that would be great, but I suspect we will need to add a Site to each of our spawned windows if we want them to behave like I described?  Thank you for any advice.

With regards,

Bill at Intrepid

Eugene Balabuev (LMD)

Using dkDocument panels with dock sites inside them is not a good idea. This is not how our package is supposed to be used and I predict you'll have a lot of issues. 

Yes, our floating dkTool panels supports docking into them, because they internally reside on forms with inplicit dock site. It is not clear why you don't like this built-in solution.

Generally, we assume that your application will have a main form with one docking site on it. Then you add tool and document panels (which you can also create dynamically at run-time), and dock them into main form's site or dock one tool panel into another floating tool panel. That is the expected usage.

Intrepid Control Systems Inc

Thanks Eugene,

As I mentioned in the first paragraph, the problem with dkTool compared with the AQDock solution is that dkTool panels do not seem to support tabs.  For example, using the style editor example, here I have docked all of the tool panels together.  We see some tabs (?) across the bottom of the window, no close buttons, no tab images.  If this can go on the top with close buttons and tab images, that would solve our problem.

Image below:

Intrepid Control Systems Inc

inline image doesn't appear to work above, attaching image file 

Eugene Balabuev (LMD)

Tabs cannot be shown at the top in tools floating sites. However you can turn on panel icons and close buttons on bottom tabs. For that you have to modify one of standard styles via editing its XML:

- Set ShowTabImage attribute to True in TabZone XML element.

- Set ShowClose attribute to True in TabZoneButton XML element.

Please learn how to deal with custom styles here:
https://files.lmd.de/downloads/tutorials/dockingpack/index.html?understanding_styles.htm

Intrepid Control Systems Inc

Thanks Eugene, 

Yes, as I mentioned I have already taken advantage of the custom styles (my screenshot is from the style editor tool).  Thank you for the tip regarding TabZone buttons, this will get us closer to what we want and we will use it.  

Thank you again,

--Bill

Intrepid Control Systems Inc

Actually TabZoneButton does not support images, but ShowClose was helpful.

For TabZone, we are already using ShowTabImage which works as expected.

Update: TabZoneButton images are working as well.  This is a good compromise and I think we can work with this.  

Thank you,

--Bill