Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


LWChris last won the day on December 24 2016

LWChris had the most liked content!

About LWChris

  • Birthday 10/14/1991

Profile Information

  • Gender
  • Location

Contact Methods

  • Website URL

Recent Profile Visitors

1,163 profile views

LWChris's Achievements


Contributor (5/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. Btw, I loved your idea so much, I created an image using the portal I made. I used my "Modify Channels" plugin to "isolate" the portal so I could put in another image inside it. First, you may want to use "Effects > Distort > Dents..." on the "disk" layer to give the outer edge a little "flaming" look. Maybe duplicate that layer and give it a beefy Gaussian Blur with a huge radius for a "halo" effect. Then on the other layer again, apply slight Zoom Blur. Finally, apply "Dents..." with low "Tension" on the two black spike layers for a more "smokey" appearance. Finally, merge all layers onto a black background: Then find my plugin under "Adjustments > Modify Channels...". Using two steps "Alpha = Identity Average" and then "Grayscale = Constant 255", you will isolate the portal. Together with two beautiful stock images from pexels (Road, Countryside), I created this:
  2. I can think of some other idea: Get the "Light Rays" plugin by MadJik (download link and installation guide in first post; don't forget to restart Paint.NET) Create a new, square image, and clear the white background Select white as primary color Create a white disk (aka filled circle w/o outline) in the middle Create a second layer above the one with the disk Select black as primary and secondary color, but set the secondary color to fully transparent Open the plugin dialog from "Effects > Texture > Light Rays...", and adjust the settings: Disable the "Use anti-aliasing" (it renders faster now and we'll blur the layer in the end anyway) Enable "Use random" Set "Reseed" from 1 to 0 (this will be important later) Set "Random factor" to 80 (the rays will now have their ends slanted) Set "Ratio of the rays" from 0 to 100 (don't worry if it looks chunky for now) Reduce the "Radius External" slider from "100" to a number so that even the rays reaching out the furthest still don't touch the disk's edge, effectively leaving the "white ring". Adjust the slider so that you're satisfied with the thickness of that ring. Memorize that number, but reduce it by about a quarter for now (so 40 becomes 30 for example). Set "Quantity of rays" from 50 to several hundred, depending on your image size. The larger the image, the greater the number of rays to make them "fine". Confirm Repeat the effect a few times, until there are just a few white dotted lines remaining in the center. Don't repeat it too often though, or the outer edge will lose its spiky appearance. Rather undo then re-apply (Ctrl+Z, Ctrl+F) the effect several times for other Using a wide black brush, paint out the most obvious white lines from the inner area that shall become pure blackness. Open "Effects > Blurs > Zoom Blur..." and set the Zoom Amount to 100 (this is why we reduced the external radius by 25% in step 7.6) Add a third layer Open "Effects > Texture > Light Rays..." again This time, select the actual external radius you memorized earlier (e. g. the 40) Repeat the effect several times again Use "Effects > Blurs > Zoom Blur..." once more, but this time with the default "Zoom Amount" of 10 You may want to try out other effects from the "Blurs" menu as well. Fragments with a high "Fragment Count" (see 2nd image) and/or "Unfocus" on "Radius" 1 work very well, too. Try around and take what pleases your aesthetics. My results (black background added for better visibility):
  3. Yes, I sometimes do that as well when it is a lot of layers, because this approach requires less switching of layers. I still have to "dump" my currently mixed color on a temporary layer though. I suggested adding a new keyboard shortcut, because introducing a shortcut "Shift+Del" that currently is not doing anything different from pressing "Del" alone is the least invasive change, especially since all it does is NOT doing a second step, so it is in a way "less destructive". So even persons who would for some reason use "Shift+Del" right now all the time would not be disturbed because it doesn't make something they used to do impossible. Another idea would be to make "Del" consist out of two steps in the history, "Delete" first, "Deselect" second so I could Ctrl+Z to get the selection back. This is the same behavior that is already used when you press Ctrl+D while drawing a line or shape within a selection. It commits the drawing, then deselects. In this case "Del, Ctrl+Z" would be my chord to "Delete and retain selection". I'm absolutely fine with that, too.
  4. Quite often I need to delete the same area on multiple layers. Currently, I always have to use a trick: make the selection, add a temporary layer and flood fill the selection as "mask", then delete on the first layer, switch to the mask, magic-wand-select it to "restore" the original selection, switch back to the second layer, delete there, and so on... That is only necessary because when you delete a selection, not only is the selected area cleared, it is also deselected. It would be really cool to have an option to retain the selection upon deletion by holding Shift to indicate that you want to delete multiple times so you need to retain the selection after clearing the content.
  5. Can't reproduce this on my machine. Chosing black primary color and orange semi transparent secondary color in a new document, I can draw any shape (tested several) with any of the three modes and it works as expected. Also, toggling the mode before finishing with Enter (or Ctrl+D for that matter) works. Can you confirm your problem in a new image with a new layer? Maybe you had some special settings such as a special mix mode for the layer or the tool and didn't realize it coincidentially produces your secondary color anyway.
  6. It's not only Chrome. It's also the hotkey in Firefox, Edge and Chrome-alike browsers such as Vivaldi. Chances are even your browser uses it.
  7. Not the biggest fan of the new icons tbh, but I see why they are necessary (and it's not your icons in particular, it's more that I dislike the "plain" style in general, it looks crude to me). The only thing I have to criticize is when you did not only change the style but also the symbol itself (e. g. when closing an unsaved document, I'm pretty sure there used to be a red cross, not a bin and an arrow). That makes getting used to the new theme more difficult than necessary. Otherwise I guess I'll get used to it. As long as you don't make the mistake of going monochrome like Microsoft did with Office and Visual Studio 2013... that was the biggest fail after SCREAMING ribbon tab headers. 😂 Thanks for the layer rotation, now I just need the 90° rotations, too, and I'm happy (rotation zoom is lossy somehow).
  8. I understand that in general for hotkeys. You wouln't want to assign "Reset to default colors" to the "Delete" key (as in deleting your custom color choices), when the same key triggers a destructive action for other parts of the program. But I think it's okay for mouse actions on totally different areas of the GUI. Also You cannot expect the same thing to happen, since you can neither "close a layer", nor "hide an open file". The action that is closest to "closing a layer" is hiding it - which would happen. The action that is closest to "hiding an open file" is closing it - which already happens. So I think it fits in the greater scheme of understanding. Thank you. I get there are more important things (like maybe updating the "Popular Feature Requests" thread? *hint* ). I hope it'll be in soon nevertheless since it's just an event binding to add.
  9. Well, middle click as a shortcut to close tabs is quite common, but I don't see how that would contradict using middle click on other UI elements with a different action. Currently, middle click behaves like left click. I'm not sure this will look very well. And no matter how big it will become, it will necessarily always be a lot smaller than the whole layer item. Also, the clickable area is already taller than the checkbox, but every time I try to very quickly toggle many layers in a row, about half of the time I activate the layer instead of hiding it. It actually may be an UI issue with the click event being routed to the wrong element for inactive and/or invisible layers, but it's hard to tell for me whether I nailed the click or am just a few pixels off when doing it fastly in a row for 10+ layers.
  10. It's a bit cumbersome to quickly toggle the visibility for many layers, because the checkbox is quite small. Nowadays where most computer mice have a middle button, how about defining middle click on a layer in the Layers tool window toggles the visiblity? This greatly increases the "hit box" for this. Thanks 😁
  11. As most people know, F5, F6, F7 and F8 hide/show the four tool windows. So how about making F9 and F10 preview keys? Pressing F9 only hides all currently visible tool windows while pressed (i. e. if you release the key they come back), so you can get a full view of the image part you're working on. Much like the spacebar temporarily enables the pan tool for as long as you hold it. F10 could be a full-on "preview". It could do the same like F9, but additionally reset the zoom to "fit canvas to screen", hide any selection, handles and cursors, and disable the pixel grid. So when you are currently zoomed in to a certain part of the image you are working on, with your tool windows flying around, simply holding F10 would enable you to get an overview over the full final image, but once you release the key, everything is back to where it was and you can pickup the editing where you left without having to manually toggle all the tool windows and hitting Ctrl+B and then later on restoring the zoom level.
  12. Rick, this feature request is about adding a function to save the list of opened images to a session file and restoring that session again. He named his various use cases to illustrate when he could use that feature. Discussing whether the use cases can be circumvented by buying a new PC or setting up a different OS configuration is not the point here. Session files could be useful in many more cases.
  13. Quite often I use the color picker tool but accidentially click with the wrong button and override the wrong color. It would be cool if I could Ctrl+Z that.
  14. If you are not too worried about making the absolutely best possible decision between which eventual color a blended pixel becomes, the method I'd use is: Select the color picker. Select a pixel from the middle of a color plane, say, the yellow one. Select the magic wand selection tool. Select a pixel in the middle of the color plane again. Adjust the Tolerance level, until you feel satisfied with which pixels will become yellow and which should remain for the adjacent colors. Press Backspace to fill all selected pixels with the primary color. You can also use the color separation (Ctrl+Shift+P) for a first reduction, too. You will probably not find a setting that immediately splits the blended edges perfectly, because if you have three colors, you'll have to allow 3 different values for red, green and blue, and therefore allow 9 colors overall, but it's quite a reduction from the original set of possible colors.
  15. Hello @Pixey, I know that Paint.NET tries to "help" by selecting the next-best visible layer when I delete layers or when the change I made in the layer properties was hiding the layer. What my reproduction steps were meant to show that this behaviour introduces a consistency issue, for example when you rename layers. Even worse is the fact that it doesn't happen when you change nothing in the properties dialogue and because it decides "Nothing to do here" and also skip the check. That means it's very confusing at times. It does not change when you unhide the layer It does change when you hide the layer It does not change when you change properties for a visible layer It does change when you change properties for a hidden layer It does not change when change nothing for a visible layer It ALSO does not change when you change nothing for a hidden layer The use case that happened to me was that I wanted to rename a hidden layer. I selected the layer in the Layers window, I pressed F4, typed the new name, noticed a typo but my right hand was too fast pressing "Enter". So I pressed F4 again, and suddenly the name was completely different. It took me a while to notice the layer had changed to the next visible one below. I did not expect "Rename" to change the active layer, because I have not actively been messing with layers or their visibilty.
  • Create New...