[Bug]: Mark ReactiveObject IObservable properties with DisplayAttribute for Winforms

[Micha-kun]

[Bug]: Mark ReactiveObject IObservable properties with DisplayAttribute for Winforms

[glennawatson]

Browsable(false) by the looks. Wouldn't that be more suitable?

[Micha-kun]

It worked! YESSS!

[glennawatson]

Is there an attribute for the annotations that makes the property grid not generate for that property. Doing a quick hunt

[Micha-kun]

Hmm... Maybe both are required (depending on the control is binded)? In DevExpress controls , at least, the one that works is [Display(Order = -1)]

[Micha-kun]

Hmmm there are other properties on DisplayAttribute that prevents to generate the column:
[Display(Order = -1)] hides the column but [Display(AutoGenerateField = false)] prevents the column automatic generation and [Display(AutoGenerateFilter = false)] prevents the column to be used on filters.

So, the correct attribute usage should be [Browsable(false), Display(Order = -1, AutoGenerateField = false, AutoGenerateFilter = false)]

[glennawatson]

anyway open to having these attributes on the class mentioned providing it can be handled by all platforms etc.

Happy to take a PR if you like and we can get it in the next release?

[glennawatson]

BTW I suspect for other platforms like WPF it'll be a good thing. WPF doesn't come with a native property grid, but almost all I know of work like the winforms one and obey those properties. Eg I suspect the problem you're having would be a issue even with the native winforms propertygrid not just the devexpress ones.

[Micha-kun]

Ok! I'm going to make a PR :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.