tieTYT

Awesome! That makes me feel better because I use the same definitions. I completely agree! I think I'm making it seem otherwise, but that's not my intent. I now understand how to avoid the behavior in my original post (see the reply I marked as the answer), now I am trying to understand how to benefit from the transparent-pixels-overwrite-visible-pixels-in-the-same-layer behavior. How have you (or anyone else) leveraged this in useful ways?

Apologies, my ignorance of proper terms is confusing my message. Whenever I have said, "transparent pixels" I meant any pixel with an alpha of zero; "Non-transparent" meant an alpha greater than zero. You never asked for my life story, but in grade school, I was taught this as the definition of transparent: "Things that are transparent are so clear you can see through them as if there’s nothing there." Sometimes I fall back to that definition without considering the context. Sorry about that. In this situation it would behave the same way as it currently works: the partially transparent pixels of the selection would completely overwrite the pixel they're covering.

TL;DR: How does the current behavior improve the user experience compared to the behavior I expected? ------------ I think I understand, but just to be sure, I'll say it in my own words. In each layer, there is exactly one pixel per "point." e.g., in a 200x300 layer, point (0,0) has exactly one pixel, point (1,0) does too, and this is true all the way to point (200, 300). If you can't see the pixel, that is because it is transparent, but it is still there. When you copy a selection, the transparent pixels of that selection are copied, too When you move the selection, the transparent pixels will overwrite the pixels that existed in that location, even if the previous pixels were visible. If I'm understanding that correctly, I'm glad I understand and this will prevent confusion for me in the future. I now see the rationale behind the behavior and appreciate the consistency with the way pixels work on layers in general. I can see now this isn't a bug but working intended. That said, I'd now like to change my "bug report" to a "feature request," if possible? I'd like to ask, is this a good user experience compared to the behavior I expected? Namely, I expected the transparent pixels of my paste buffer/selection to leave the non-transparent pixels the way they were. Instead, they overwrite the visible pixels. If the current behavior is a good user experience, can someone explain to me why? I can't think of a situation where transparent pixels overwriting non-transparent pixels would be useful.

Sorry for the late reply. Both of those solve the problem, thanks. Is this a bug? If it's not a bug, can you help me understand when the behavior in my GIF is advantageous? It'll help me understand when I should use it. Thanks!

Thank you! I appreciate your fast response. I'm having a hard time following this thread, probably because I'm not used to using this forum. Are you saying that recently updated Windows (in my case, Windows 10) won't be able to use this plug-in and less they install the patched version of paint.net? I ask because as far as I can tell I followed these steps correctly, but I'm not seeing any of the new plug-ins described in the original post. I'm using paint.net 5.0.12 and have .net sdk 7.0.403 installed.

@Ed Harvey Hello, I've tried to install this plug-in and I'm not sure if it's working correctly. Would it be possible to add a screenshot of where to find this plugin in the paint.net menu? It would help people like me to know if it's working or not. Thanks for all the effort you've put into these plugins.

I made an animated GIF to show what I'm seeing: I don't know why that embedded link isn't working, so here's a direct link to the GIF: https://imgur.com/gallery/ivkyvFu Hopefully that GIF explains everything, but I'll write a bug report, too. Steps To Reproduce: Create a new image Create a new layer with a transparent background Create a line in that layer Ctrl+A (to select all) Ctrl+C (to copy selection) Ctrl+V (to paste) Drag the selection around Expected behavior: Since the layer has a transparent background, the selection should not cover the line from step 3. Actual behavior: The selection covers the line from step 3. Additional context: This is probably a very popular use case so I'm assuming it is working as expected? If that is the case, Is there a way to change this behavior? --------------------------- I might be reporting a duplicate of this, but most of the context has been lost so I can't tell:

I frequently press ctrl+C to copy an image and try to paste it elsewhere (not always within paint.net) only to realize I copied a single layer instead of the whole image. While this is a minor inconvenience, I would use a setting that swapped these keyboard shortcuts if it existed. Therefore, I thought I would propose this feature request because others might feel the same. In lieu of this existing, I could probably create an AutoHotKey script to achieve this. Thanks!

I often use paint.net for a single project at a time. One project may use a particular font while the next one uses something completely different. With the current Settings -> Tools, I would need to change the defaults for each new project, but it would be more convenient if I could just assign certain tools to default to the last settings I used. This is similar to how the Windows "Snip & Sketch" tool works: if I change the brush thickness, the next time I use the application it defaults to that last brush thickness. I'm not advocating for taking away any existing functionality; that is, I like the ability to set the default to a specific value for certain situations, especially the default tool. Thank you for your consideration.