This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
(Logical follow-on from )
As part of my solution for (https://www.mindscape.co.nz/forums/Thread.aspx?ThreadID=3026), I've spun up a number of dynamically-generated properties on my selected object. Unfortunately, these properties can be added and deleted by the user. This brings me basically to the problems listed in (https://www.mindscape.co.nz/forums/Thread.aspx?PostID=9017). However, in this case I: 1) cannot modify the selectedobject/selectedobjects values (null then reset), as they are set using bindings to things in another control. Now I totally agree that the old .Refresh() thing isn't a NICE solution, but right now I don't really have ANY solutions. Ideas? |
|
|
Is manually calling a hypothetical PropertyGrid.Refresh method a viable solution for you, or would you need us to automatically refresh the metadata as you make changes? Could you live with calling Refresh manually, even if you'd prefer the automatic refresh? |
|
|
A manual solution would be just peachy (so long as it could cope correctly with a property vanishing from just one entry in a selectedobjects collection). |
|
|
I've added a Refresh method to the PropertyGrid control, which basically forces it to regenerate all the rows. This will therefore pick up any changes to the metadata (properties added, removed or changed). It's a pretty blunt instrument though: let us know how you get on and whether we need to refine it (no promises though!). The new method will be included in the 23 April nightly build. It is marked as Advanced for intellisense purposes and may therefore not show up in intellisense depending on your IDE settings. |
|