Hello all I am getting back to you for an issue with the ASPXGroup property editor. After ticket 26444 i have been using this property editor to display non persistent entities. But when i tried to apply the same logic to a complex persistent entity i am getting exception when opening (and thus loading) any of the groups (nested views) inside the main detail view with text "Exception occurs while assigning the 'DetailView, ID:...' view to NestedFrame: Value cannot be null." (i include the full error in the attached text). My guess is the nested frame does not know what object to load? Any ideas for what's wrong?
after a bit of investigation seems to be an aspximageproperty editor that causes the problem above. Still with default view it is rendered ok (with no value as it is empty) so should also inside the aspxgroup.
Sasha (Xafari Support)Client
Hello Greg,
Thanks for reporting the issue. We are going to investigate it. Give us some time.
Best regards, Sasha.
Sasha (Xafari Support)Client
Hello Greg,
We are unable to reproduce the issue with the steps you provided. Could you please provide us with the following info: detailed steps (class, settings) to reproduce the problem? And you can try to use the byte[] type instead of the Image type and set the property PropertyEditorType=ASPxImagePropertyEditor for DetailView.
Thanks, Sasha.
Γρηγορης Τσολακιδις
Hello Sasha,
The property was already byte[] and even when i switched to default ASPxImageEditor from DevEx it produces the exception. Only when this property is in ASPxGroupEditor. When outside as a stand-alone property editor in a detail view it is ok.
For your convenience i created a simple project to demonstrate. Only a simple domain class TestClass with several properties and a byte[]. In the detail view you see the default image property editor ok but when pressing to open group3 that contains the same editor you get an exception.
Please have a look and get back to me with suggestions.
We apologize for the delayed response. In your sample and our test samples this issue not occur for Image type. The byte [] has been as an alternative, but it requires additional settings and and changes to work correctly (as example Load image from byte[] into ImageEdit).
We are going to solve current issue with byte[] in next release. Let us know if the issue with type of Image still topical.
Best regards, Sasha.
Γρηγορης Τσολακιδις
Hello Sasha,
Indeed when converting byte[] to System.Drawing.Bitmap the issue was resolved. But since DevExpress supports direct byte[] to various image format conversion it would be nice to keep this with your controls as well.