What the new version broke:
One or more properties that we were using were eliminated (I don't recall which ones). Beyond that we don't have the time to regression-test the entire form again (the property grid is in a form with over 40,000 lines of associated code, and there are over 900 test cases that would have to be put through the ringer again). All of that spells "it ain't gonna happen".
The reason I did the editor definition that was was because it was mandated that we would use a form that already existed in the application. Since we are in bug-fix stage (as opposed to new development stage), I came up with the quickest fix I could. The documentation of the toolkit (as it exists on CodePlex) is beyond bad, so coming up with custom editors is problematic. I changed the editor definition property to use the transient property I mentioned in my original post. The problem is that I can't do the expected dot-notation to burrow into the expandable object.
One or more properties that we were using were eliminated (I don't recall which ones). Beyond that we don't have the time to regression-test the entire form again (the property grid is in a form with over 40,000 lines of associated code, and there are over 900 test cases that would have to be put through the ringer again). All of that spells "it ain't gonna happen".
The reason I did the editor definition that was was because it was mandated that we would use a form that already existed in the application. Since we are in bug-fix stage (as opposed to new development stage), I came up with the quickest fix I could. The documentation of the toolkit (as it exists on CodePlex) is beyond bad, so coming up with custom editors is problematic. I changed the editor definition property to use the transient property I mentioned in my original post. The problem is that I can't do the expected dot-notation to burrow into the expandable object.