Hi,
question is simple:
will image resources be properly disposed automatically? As you can see I'm clonning modified image here and saving it to session, this custom property before setting value to session checks if there is object already, if so it calls Dispose on it.
My use case is that I trigger save on server from client side, on OnSaved client event I cause manual postback. This is needed because I need to modify the Viewstate once image is saved. I tried in server side's on saving, but Viewstate was reverting back, so this workaround was done.
Client side:
in button's onclick server handler I pull image from session and save it with preprocessing I need, then remove session object.
Same applies to pageImageEditor_ImageLoading where this image is set:
as soon as on that view I have image editing functionality for all pages, I force ImageEditor to load new image for page by:
pageImageEditor.ImageUrl = string.Empty;
otherwise it uses previously displayed image.
So does the handler properly disposes it's resources in my use cases?
Thank you!
question is simple:
protected
void
pageImageEditor_ImageSaving(
object
sender, ImageEditorSavingEventArgs args)
{
// maybe check is not required, but just in case
if
(args.Image !=
null
&& args.Image.Image !=
null
)
{
// saved modified image clone to session for 'btnSaveImageChangesInternal_Click' usage
SessionObjects.ImageEditorHelper.TempStorageForEditedProjectContentElementImage = (Image)args.Image.Image.Clone();
}
args.Cancel =
true
;
}
will image resources be properly disposed automatically? As you can see I'm clonning modified image here and saving it to session, this custom property before setting value to session checks if there is object already, if so it calls Dispose on it.
My use case is that I trigger save on server from client side, on OnSaved client event I cause manual postback. This is needed because I need to modify the Viewstate once image is saved. I tried in server side's on saving, but Viewstate was reverting back, so this workaround was done.
Client side:
function
imageEditorOnSaved(sender, e) {
$(
"#<%= btnSaveImageChangesInternal.ClientID %>"
).click();
}
function
saveChangesInImageEditor()
{
var
imEditor = $find(
"<%= pageImageEditor.ClientID %>"
);
imEditor.saveImageOnServer(
"<%= Guid.NewGuid().ToString() %>"
,
true
);
}
in button's onclick server handler I pull image from session and save it with preprocessing I need, then remove session object.
Same applies to pageImageEditor_ImageLoading where this image is set:
protected
void
pageImageEditor_ImageLoading(
object
sender, ImageEditorLoadingEventArgs args)
{
..
....
......
using
(EditableImage image =
new
EditableImage(imgPath))
{
args.Image = image.Clone();
args.Cancel =
true
;
}
}
as soon as on that view I have image editing functionality for all pages, I force ImageEditor to load new image for page by:
pageImageEditor.ImageUrl = string.Empty;
otherwise it uses previously displayed image.
So does the handler properly disposes it's resources in my use cases?
Thank you!