Hello
Just to be sure ...
is it necessary to develop my own UITypeEditor if I want edited a property
define with Enum type in PropertyGrid during design time
For example : Control.Anchors is editing with
System.Windows.Forms.Design.AnchorEditor (with specific visual effect ...)
If my property is Enum type >> Visual Studio and PropertGrid show a combobox
to change the value of my property > Perfect !
on enum property with flag attribute, It would be very nice if Visual studio
show the same comboBox with multiple selection allowed
thanks for your help
joeycalisay - 21 Feb 2005 01:06 GMT
The AnchorStyles enum and has its own AnchorEditor which drops a custom
control (AnchorUI)

Signature
Joey Calisay
http://spaces.msn.com/members/joeycalisay/
> Hello
>
[quoted text clipped - 13 lines]
>
> thanks for your help
Craig Vermeer - 21 Feb 2005 13:20 GMT
Stephen Toub has a good implementation of a UITypeEditor for flagged
enums on GotDotNet :
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=5983093a-
9a83-400e-8f9b-23bf07bd0da9
> Hello
>
[quoted text clipped - 13 lines]
>
> thanks for your help
azerty - 22 Feb 2005 22:56 GMT
Thanks a lot for your help : it is exactly what I searched !!
I develop for Pocket PC device.
So If I want use correctly this editor, it is necessary to include it in
another assembly wich don't use System.CF.Windows.Forms
If I do not this >> Visual Studio throw an exception when I try do show the
editor in PropertyGrid because type mismatch !!
In fact, when an assembly use for example "System.Windows.Forms" and
"System.CF.Windows.Forms" it would be perfect If I could say to compilator
for one code line : "hey, guy, don't use "System.CF.Windows.Forms" I prefer
you use "System.Windows.Forms")
Any one may be known an issu to do this ??