I only use AnchordockingDsgn not both AnchordockingDsgn and anchordocking. I noticed that with a lot of component in my form I got a lot of problems with my form with both packages.
AnchorDockingDsgn uses AnchorDocking. So you do use both.
In general the *Dsgn packages are usually the registration part into the IDE. And they always pull in the non-Dsgn package
AnchorDocking contains all the code to have docking. You could use AnchorDocking in any project of your own.
But AnchorDocking does not tell the IDE how to use it. AnchorDockingDsgn changes the IDE to make the correct calls to AnchorDocking.
AnchorDockingDsgn you can't use in your own app (well not without a lot of workarounds). AnchorDockingDsgn expects to find the IDE code in the app.
And AnchorDocking is for all forms except the designer. AnchorDocking can not dock the designer.
That is where DockedFormEditor comes in. And you can use DockedFormEditor with or without AnchorDocking.
And last not least: Make sure you do not have anything ...sparta... in your installed packages.
Well, very last.... If you get issues, and if you can't find an existing bug report => create a bug report.
(Ideally tested against 2.3)
Which should have at least one of...
- steps to reproduce (can include a project, which if opened will cause the issue)
- stacktrace with line numbers and unit names (if it is a crash)
Without good bug reports, it is not likely to improve much.