Kanai Posted May 11, 2019 Share Posted May 11, 2019 (edited) There seems to be a problem regarding the "Move Selected Pixels" tool to resize images with transparent edges down, one (or rarely two) ghost selection can appear. This problem usually isn't apparent unless you use the "Magic Wand" tool at 0% Tolerance. If you scale a selection down, one of two selections of the transparency will be selected, with the original boundaries of the selection (that was scaled down) becoming a ghost selection. These two different selections both show they have 0 opacity when colour picked, but both have their own Hue and Value/Brightness values, the ghost selection has 0 Value and is completely black, while the outside selection will contain the Secondary colour that is on your palette with 0 opacity. Having black as your Secondary colour when scaling down images eliminates this bug, while using any other colour does not. If you can't really understand what I have to say, watch this video of me showing off the bug. Edited May 11, 2019 by Kanai Forgot something. Quote Link to comment Share on other sites More sharing options...
toe_head2001 Posted May 11, 2019 Share Posted May 11, 2019 That's not really a bug, and is the intended behavior. Quote (September 25th, 2023) Sorry about any broken images in my posts. I am aware of the issue. My Gallery | My Plugin Pack Layman's Guide to CodeLab Link to comment Share on other sites More sharing options...
Kanai Posted May 11, 2019 Author Share Posted May 11, 2019 Hmm, what's the point of that though? Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted May 11, 2019 Share Posted May 11, 2019 The bug is that Magic Wand isn't using premultiplied alpha for its calculations. Transparent "black" is the same as transparent anything else, and should be treated as such. It'll get fixed, just not yet. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
toe_head2001 Posted May 11, 2019 Share Posted May 11, 2019 Oh. My mistake. I thought the opposite conclusion had been reached in the past: RGB values are different, so treat the pixels as different. I'm glad I was wrong though. I too would prefer all transparent pixels to be treated the same. Quote (September 25th, 2023) Sorry about any broken images in my posts. I am aware of the issue. My Gallery | My Plugin Pack Layman's Guide to CodeLab Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.