Once you commit to creating a custom property editor, you can basically do whatever you want.
That process involves implementing some interfaces and applying some attributes I don't quite remember. (I did this for 6 years, but that was 5 years ago.) At a high level, a "UI Editor" for a control is a UserControl that gets a property value and has to publish changes to that value in a particular way. So whatever thing you can imagine is possible.
But I re-iterate: overcategorization is worse than no categorization. I haven't used the "category" view for years to edit properties, I like them alphabetized so I can get to the ones I want. If your control takes 4 extra clicks to edit some property, I'd much rather use someone else's that takes fewer clicks.





Reply With Quote
