NET PROPERTY GRID CUSTOM TYPE INFO CODE

There's another set for of configuration for the Previewer on the right but that's not relevant for the discussion here. An AceEditorConfiguration property on the User Control for persistent storage of the config values.An AceEditorConfiguration class that holds editor specific config values.The control dropped on a form looks something like this:įor the discussion here, I'm focusing on the Editor specific configuration which concerns the operation of the left hand pane in this dual pane control. You can drop the editor onto a form, set the EditorText and you have a rich text editor to work with in your app.

So my specific scenario is a UserControl that contains a Markdown Editor that has both an editor and previewer in a dual pane interface. So you can think of this as a sort of refresh of an old topic 😄 An Example of a nested Control Sub Object No, this is not a new topic obviously, but it's getting harder to find this sort of information given that WinForms is uh a bit dated these days and some of the old information is slowly either disappearing off the Internet or at least not being indexed very well anymore. the WinForms designer doesn't handle nested properties in the Property Grid automatically, and so there's a bit of extra work required to make nested properties work at design time and that's the focus of this blog post.

Sub-objects delineate functionality much nicer, and make it easier to find what you're looking for.īut.

NET PROPERTY GRID CUSTOM TYPE INFO CODE

This is especially relevant for the editor which needs to serialize the data to JSON to pass it into the HTML/JavaScript code inside of a browser.įor the designer it's probably fine to use a ton of top level properties since you can use the category property, but for code having 50 different properties scattered alongside the myriad of already busy user control properties it's a pain when you bring up IntelliSense and end up looking for the right editor setting to apply. So rather than having to pass the entire control I can just pass these state objects. The application also passes these config objects to the underlying editor and previewer, and the object acts as the persistent state of the control. Rather I want to get a child property - or several of them actually - to handle the more specific sub-configuration tasks with cleaner delineation of responsibility. One of the issues that I ran into is that I have a ton of configuration for this control and I didn't want to expose all of it at the top level control object. It's been a while since I've used WinForms and for the last few days I've been working on a new Markdown editing control for an application.

Net property grid custom type info