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
|
It's possible to change the selected object frequently in my application, and I'm making use of several somewhat complicated custom editors. I'm seeing a noticeable delay as the property grid generates new controls on the UI thread (and an upsetting number of allocations -- memory usage is very 'spikey' when viewed in perfmon). Would it be possible to do some caching of controls? (Is this possible already?) I can see why this could be undesirable default behavior since an application could use an extremely large number of objects/property names, but I suspect that it's common for an application to allow instances of a relative small number of classes to be displayed in the property grid (on the order of tens). In these cases, it would make a lot of sense to cache. |
|
|
|
|
If other people are running into this problem, one workaround is to use two properties. The application binds to the first, the property grid binds to the second. This lets you throttle the number of assignments to the property grid's SelectedItem.
|
|
|
|
