We have two problems with the image editor.
1.
Image editor's has a property Image history which has a Image History depth. If set for example 3, the image editor does not depth setting.
On Image editor loaded event handler we set the following.
this.RadImageEditorUi.ImageEditor.History.Depth = 2;
However the image editor Keeps more then 2 history in that case.
2.
We also saw some memory freeing problem. If a lot of steps are done for some tool, the application reaches up 1GB+ quite easily and It does not free up the memory soon. This problem can be easily reproduced with "WPF Demos.exe", on the image editor drop a large image(ofcourse within the limits of allowed size MaxHeight = 2100;MaxWidth = 3900;) use some tool e.g. rotate and the memory could rise to 1gb+
Does anyone else see/encountered these? Is it possible to fix this?
1.
Image editor's has a property Image history which has a Image History depth. If set for example 3, the image editor does not depth setting.
On Image editor loaded event handler we set the following.
this.RadImageEditorUi.ImageEditor.History.Depth = 2;
However the image editor Keeps more then 2 history in that case.
2.
We also saw some memory freeing problem. If a lot of steps are done for some tool, the application reaches up 1GB+ quite easily and It does not free up the memory soon. This problem can be easily reproduced with "WPF Demos.exe", on the image editor drop a large image(ofcourse within the limits of allowed size MaxHeight = 2100;MaxWidth = 3900;) use some tool e.g. rotate and the memory could rise to 1gb+
Does anyone else see/encountered these? Is it possible to fix this?
1 Answer, 1 is accepted
0
Hi Alexander,
There seems to be an issue in the way history's depth works. I logged this for further revision and fix and updated your Telerik points in appreciation of the report. You can follow our progress on the matter in the Ideas & Feedback portal at History's Depth property is not respected.
As to the memory allocation you mentioned, I can't seem to replicate such behavior. Would it be possible to send us exact steps that reproduce the issue and the image you are testing this with?
I'm looking forward to hearing from you.
Regards,
Petya
Telerik
There seems to be an issue in the way history's depth works. I logged this for further revision and fix and updated your Telerik points in appreciation of the report. You can follow our progress on the matter in the Ideas & Feedback portal at History's Depth property is not respected.
As to the memory allocation you mentioned, I can't seem to replicate such behavior. Would it be possible to send us exact steps that reproduce the issue and the image you are testing this with?
I'm looking forward to hearing from you.
Regards,
Petya
Telerik
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.