Here is some information that should be useful:
As all Prometheus controls are contained in a single DLL, RadEditor's default tools file is also contained as a built-in resource there. The tools file contains both default tools and default modules.
When the developer adds tools in the codehbehind using the editor API, the default tools file is loaded, yet it is not cleared. This is based on the assumption that the developer has full control over the API and can easily clear the default tools before adding new ones.
When an external ToolsFile is used - then editor modules will be loaded in the editor, only if they are present in the toolsfile.
Now, there seems to be an incorrect statement in your scenario #3 - this is not the intented behavior, and we were not able to reproduce it either
Case by case, here is update on each scenario:
1) Just using the toolsfile - the modules area does not appear - CORRECT
2) Just adding tools dynamically - modules area appears - CORRECT, the default tools file is used, and modules exist there.
3) Just adding tools dynamically and using RadEditor1.Modules.Clear - modules area appears - Not able to reproduce
. In our tests using RadEditor1.Modules.Clear
does clear the modules, in all cases.
4) Using the tools file, clearing the tools and then re-adding them dynamically - the modules area does not apear. - CORRECT
. You use a tools file with no modules, so no modules will appear, regardless of whether you clear the tools or not
In case you observe different behavior than the provided in these explanations, please send us a sample project that reproduce the issues and we will examine it.
the Telerik team