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 seemed the property grid does not work with TypeConverter derived from the ExpandableObjectConverter. public override TypeConverter.StandardValuesCollection GetStandardValues(ITypeDescriptorContext context){} did not pass in the selectedobjects on the parameter "context". Same kind DataObject is working with Windows Form's PropertyGrid. I am including the DataModel and the Window's form application and wpf windows with your propertygrid. For the property Grid, we need to have the same behaviour as in the windows form application. Please let me know if I did something wrong there and how to fix them. Same Data Object works for windows' form propertygrid perfectly though |
|
|
|
|
Hello Gordon, No, you're not doing anything wrong; the issue is that we do not always have the information available to populate an ITypeDescriptorContext. However I have looked into your use case and I have implemented an update to the PropertyGrid control so that you will now receive a basic context (only usable for the Instance and PropertyDescriptor properties; the Container property and GetService methods will return null). This update will be included in the next nightly build, which you can get from the Downloads page from about 1200 GMT. Please let us know if you still see problems after updating (you'll probably need to do a clean and rebuild of your solution to make sure VS picks up the updated DLL). By the way, a minor tip -- you don't need to reference the .Design and .Design.10 DLLs in your project. Those DLLs are for design-time support only; they're not used by applications. |
|
|
|
|
Thanks a lot for your quick response, IVan. What is the difference between you formally released products and nightly build? Is that fully tested too. How safe for us to use your daily builds? Thanks |
|
|
|
|
Nightly builds don't go through a formal acceptance test, but they do go through the full suite of unit tests. So the core DLLs are normally highly reliable, but sometimes there are rough edges like we forget to include a sample file or we haven't added a Toolbox icon for a new control; and of course fixes or new features may sometimes require a couple of iterations to complete or to shake out bugs. Nightly builds are our standard mechanism for shipping feature requests and bug fixes, and with the occasional shameful exception our customers have run into very few problems using them. It is generally very safe to use these builds, but of course it is wise to regression test your application when upgrading to a nightly just as you would for any new version, even a 'formal' one. |
|
|
|
|
I installed Mar 8, build, but it still did not solve my problem. It is not crashed anymore, but it cannot expand the objects. Please compare the windows form's application and wpf's application in the zip file to see the difference. |
|
|
|
|
This will be addressed in the next nightly build. Note that we display collections in a different way from the WinForms property grid. If you want to keep the WinForms-style collection editing dialog, you will need to implement that in your own code and hook it up via an editor. |
|
|
|
|
I tried the Mar 9's build. It still does not refresh properly. For example, you change the mean value it will show on the Prior Probability Distribution only when you choose Custom and then choose the Normal Distribution. When you click + on the custom, it will not show right away. |
|
|
|
