Open jhwheuer opened 3 years ago
Hello jhwheuer, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
Thanks, @jhwheuer for bringing this here. Looping in @HHChaos to provide insight on this scenario 🤔
This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.
@HHChaos any thoughts on what might be going on here?
I am using
ImageCropper
in an app that allows the user to crop multiple bitmaps before submitting the changes in one batch. The user needs to switch between bitmaps.I let her select bitmaps through a
ListView
. Every time theListView
has a newSelectedItem
, I grab the currentCroppedRegion
off theImageCropper
and store it with the bitmap instance. Then I load the newly selected bitmap intoImageCropper
and try to set the cropped rect. The bitmap initializes the stored Crop to 0/0/Width/Height...When switching between bitmaps I notice that the
ImageCropper
produces wrong crop rectangles and sometimes even artifacts of underlying canvas pixels... Do I need to wait for the load and process to finish???Anything I am not getting?
Maybe it would be a good idea to make two changes:
LoadImageFromFile()
an optional parameterRect?
that identifies a desired cropped regionThis was posted as a bug in https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/issues/400 and was suggested to be posted here as well...