Resize() is broken.
See original GitHub issueResize may be broken.
var mm = new MagickImage(MagickColors.Black, 512, 1);
Console.WriteLine(mm.Height); // result: 1
mm.Resize(512,512);
Console.WriteLine(mm.Height); // result: 1
mm.AdaptiveResize(512,512);
Console.WriteLine(mm.Height); // result: 512
When resizing from 512x1 to 512x512, Resize()
returns the same result, but AdaptiveResize()
works (but takes much longer, as expected).
Same for any resolution, not just 512x1. Seems to be affecting all builds 7.2 and above. Not tested on older builds.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
jquery - $(window).resize() not working
The function works fine when i refresh the screen, but the $(window).resize() doesn't seem to work. jQuery(document).ready(function($) ...
Read more >ScrollSmoother + ScrollTrigger resize broken? - Page 2
I have the same issue, scrolltrigger is working after resizing. I can't share a codePen, it's on a localhost. - My version of...
Read more >Resizing window applications broken
The issue you're experiencing with modifying the window size of your Windows apps might be due to a corrupted system file. That being...
Read more >Image resize in browsers is broken
If you've ever tried to downscale an image using a web browser, you've probably noticed that it looks like it's been through a...
Read more >Image->resize() not working - Solved
I just migrated a dev page to a live page and apparently the image->resize() function does not work anymore. PHP is set to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think it would be a good idea to add the extra enumeration overload. The API already has a method for what you want. I think it would just clutter the overloads.
I added the documentation to the summary block so it will show up in intellisense. When this is added to the remarks it will not appear during typing. This will appear in the next release.
Sounds good. Thanks! 🙂