Reply to thread

just a quick comment to what is supported and what not.... I implemented a feature that uses .NET reflection to look inside the dlls and query for supported controls, etc. Its just not completely done. I want to use it as a guideline for the developer, not as a limitation. So I don't plan on limiting the controls but want to offer kind of a validation.

For changing the control-type.... Don't think its possible since each control-type is implemented in a separate class so I would have to convert one class into an other (not possible like that). Maybe I can implement a feature that copies most of the properties from one control to another. That would ease the work but is too much for now.