Rick Brewster

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Rick Brewster

  1. The title bar is supposed to turn white when the window is inactive. That's just what Windows does for non-UWP windows.
  2. Here's an "effect" that Tom wrote. Basically what it does is let you write code that is compiled on the fly and that is then executed in the Paint.NET effect engine. This is the same plugin that we made available for Paint.NET v2.1, but it has been updated to work with Paint.NET v2.6 (and later). With this you can implement almost any type of effect you want if you have the programming and mathematical talent to do so. This plugin works by presenting you with a simple text editor that you can use to type in C# code that is then compiled and executed (rendered) as soon as you stop typing. Please note that this is experimental technology and is not meant to provide a robust development environment. It is perfect for rapid prototyping and very useful for educational purposes including teaching computer graphics. This plugin especially benefits from Paint.NET's extensive multiprocessor and multicore support. For instance, if you are interested in rendering high resolution fractals on an expensive workstation, this is the way to do it! The code you write is automatically multithreaded and the workload is spread across multiple CPU's resulting in near linear performance scaling (4 CPU's = almost 4x faster). Download: http://BoltBait.com/pdn/codelab/ Note: BoltBait is the current maintainer of CodeLab. Help file: http://BoltBait.com/pdn/codelab/help/ Tutorials: Overview Tutorial 1 of 4 Tutorial 2 of 4 Tutorial 3 of 4 Tutorial 4 of 4 Tutorial 5 of 4 Tutorial 6 Tutorial 7 Sample Code Russian If you speak Russian, download here: http://forums.getpaint.net/index.php?/topic/29995-a User ReMake maintains the Russian version. Post enhancement requests/bug reports of the Russian version on that thread. With CodeLab, you can... Work with complicated displacement filters: Parametric images: High resolution fractals:
  3. "Remove focus from the program" ? I've never heard of that setting.
  4. Color palettes disappeared

    Change the language back to English then. The Palettes folder's name is localized, so if the language changed for whatever reason then Paint.NET will be looking for your palettes in a different location. When you change the language from within the app (in Settings) it will try to rename things so you don't have to worry about this. You might just see them in Documents/paint.net User Files/Palettes ....
  5. Love this Dark Mode! Two requests.

    I think they're supposed to illustrate the drop shadow and how it's a little awkward
  6. Okay but what are the settings that you used
  7. Love this Dark Mode! Two requests.

    No? Why on earth would you need to be constantly switching back and forth between the two? Also, if you leave the setting as Default within Paint.NET, you can use the Windows 10 Settings to switch between Light/Dark mode. That's pretty darn convenient. As for the drop shadow, I'm thinking about ways to improve it. It can look weird and get in the way sometimes.
  8. What exactly are your Theme settings in Windows? Did you use any utility to "hack" the color values? I got another report from someone who said they used a registry editor or something so they could specify a true black #000000 color
  9. This update fixes one major bug in Edit -> Paste that was introduced in 4.0.20. If you’re using the Windows Store release, you should get the update automatically within the next few days. For the Classic release, you can use the built-in updater by going to ⚙ Settings → Updates → Check Now. You can also download it directly from the website. Change log: Fixed a bug where a pasted image would be clipped after choosing "Keep canvas size" Enjoy!
  10. No, this is a different visual glitch. I think I've seen this though. Try going into the Windows theme settings again and "jiggle the handle." That is, change your settings to something else and then back again. Do this for the window color, and also for the "show accent color on: title bars" setting. Sometimes this glitch happens with a fresh install or a freshly upgraded install of Windows 10. I think.
  11. paint.net 4.0.20 is now available!

    Locking and un-pinning this post. New updating incoming.
  12. This update adds a new Dark Theme, significantly improves High DPI support, adds Explorer thumbnails for TGA and DDS image types, and also includes a whole lot of small improvements and bug fixes. If you’re using the Windows Store release, you should get the update automatically within the next day or so. For the Classic release, you can use the built-in updater by going to ⚙ Settings → Updates → Check Now. You can also download it directly from the website. Changes: New: Dark Theme support New: .NET Framework 4.7 is now required, and will be automatically installed if needed New: Explorer thumbnails are now supported for TGA and DDS file types Fixed and Improved: High-DPI support throughout the application Fixed: Color Picker tool was not always honoring the "Switch to previous tool" setting Fixed the arrow keys not working properly until the second shape (or line/curve) was drawn. Reported here: https://forums.getpaint.net/topic/112145-moving-points-in-lines-not-working-how-its-supposed-to/ Fixed the zoom slider being "wiggly" while being dragged around Fixed a glitch with the mouse cursor (resize handle) at the lower-left corner of the main window Fixed a crash in the Shape tool renderer (BadNumberException via ID2D1Geometry::GetWidenedBounds) Fixed a hang in the Frosted Glass effect that was reported here: https://forums.getpaint.net/topic/112005-frosted-glass-hangs-indefinitely-on-a-1×1-pixel-image/ Fixed a hang in the Levels adjustment that was reported here: https://forums.getpaint.net/topic/111629-hang-bug-in-a-levels-tool/ Fixed a rendering issue in the Move Selected Pixels tool that was reported here: https://forums.getpaint.net/topic/112187-selections-out-of-bounds-use-the-out-of-bounds-pixels-when-resizing/ Fixed: Canvas now processes WM_MOUSEHWHEEL, which was preventing some horizontal mouse wheels and trackpad swipe gestures from working properly Fixed: Plugins will no longer completely crash the app on Windows 10 S (note, however, that plugins other than custom Shapes do not work on Windows 10 S) Fixed: a data loss bug when saving very large images (greater than 4GB). Reported here: https://forums.getpaint.net/topic/111823-large-image-save-bug/ Enjoy!
  13. Resizing bug

    I am patching this. I know it's really annoying.
  14. Resizing bug

    There's a new bug in 4.0.20 that I'll be fixing soon.
  15. (this is copied from the blog post I just made: https://blog.getpaint.net/2017/09/29/paint-net-is-now-available-on-the-windows-store/ ) Version 4.0.18, which I just announced, is now available on the Windows Store! The standard price is currently $8.99, but I’ve put it on sale for $5.99 $4.99 until the end of October. You can also make use of the 30-day free trial to get started. (It may take a little bit of time before you can search for Paint.NET on the Windows Store. I’m told that things take up to 24 hours to “propagate.”) Get it on the Windows Store: https://www.microsoft.com/store/apps/9NBHCS1LX4R0 Wait, it’s not free? Correct! The Store release of Paint.NET is not distributed free-of-charge. This allows many things to converge and solves a lot of problems, while still providing value for new and existing users (err, customers?). The “Classic” release will still be available and kept up-to-date on the same schedule as the Store release. … Well, I’m not gonna pay for it. That’s fine. Just use the “Classic” version like you always have. It’s worth checking out what the Store release has to offer though. Maybe you’ll change your mind, but if not … ¯\_(ツ)_/¯ And you can still send a donation if that’s your preferred way of providing financial support. This is actually more effective because Microsoft does take a 30% cut of every transaction that goes through their Store. There are some important advantages that the Store release comes with: Automatic background updating. The first advantage is a really big one, in my opinion. Paint.NET already has a best-in-class update experience (“Install when I exit”, thankyouverymuch), but having updates be fully automatic and transparent is much better. Now whenever you launch Paint.NET it will definitely be the latest version. No more procrastinating the update because you’re already busy with other stuff. No more bumping into a crash that was fixed yesterday or last week (or last year … *cough* ). The Classic release checks about once every 10 days for updates, so if you move to the Store release then you’ll probably have updates several days sooner than usual (on average). Easy Installation. The second advantage is that, once purchased, it’s really easy to get Paint.NET installed onto any new device. Everyone knows that installing “classic” desktop apps on Windows is a pain, especially when setting up a new PC. But for Store apps, it’s just so much easier: go to the “Store” app in Windows 10, click on the “…” at the top right, then click “My Library,” and then just click on the little download button next to Paint.NET (and on any other apps you need to install). Wait a little bit for the download and installation and you’re done. (There’s probably a better way to do this … it’s just the first method I found that I could verify quickly enough and be confident about.) (Store apps also come with the wonderful advantage that they can’t install browser toolbars. They can’t change your web browser’s home page. They can’t do all sorts of things that would pollute your system. Store apps don’t get to provide their own installers full of sneaky check boxes that may or may not install various crapware. Paint.NET has never and will never do anything like that, but for many other apps it has been a very slippery slope over the years.) Reliability. The Paint.NET installer and updater are based on Windows Installer (“MSI files”). Over the years this has proven to be an unreliable foundation. Every update I put out comes with a very small chance that a very small number of users will be unable to install the update, and that it will break their existing installation, and that they’ll be unable to reinstall – until they follow a set of crowdsourced troubleshooting steps that usually (but not always ) solves the problem. I’ve never been able to reproduce this, and I’ve never discovered the reason this happens. This problem goes away completely with the Windows Store release because of the way the package manager and application model works. So … why charge for it now? Over the years, I’ve been told over and over that I should be charging for Paint.NET and that people were willing to pay me for it. Accepting donations, the equivalent of a virtual “tip jar,” was a good way to accommodate this without having to develop or integrate a payment system along with serial numbers and piracy and all of that anti-fun. I’ve always been more interested in people having Paint.NET than ensuring that it has reached its full monetization potential (it’s been partly a lifestyle choice). However, statistically speaking, not very many people actually send a donation. The numbers are actually incredibly tiny, and it’s only because Paint.NET has such an enormous user base that I’m able to see much from this. This is totally fine though – the psychology and statistics of a system like this just lean heavily against it being very lucrative, and I had long ago made a lifestyle choice to not go down the other fork in the road towards business and marketing. Don’t get me wrong: getting donations is actually very rewarding! If someone likes Paint.NET so much that they’re willing to go to the PayPal website, punch in their details, and send me money, then that really says a lot about how much they appreciate it. I’ve had folks tell me that they promise to donate when they have money, and I’ve always told them to just tell all of their friends about it instead and to not feel indebted. I’ve wanted to put Paint.NET into the Windows Store for awhile, but I couldn’t determine a way to monetize it that fit in with the existing distribution philosophy. Microsoft won’t allow you to accept payments or solicit donations except through their billing system, which meant that the Help menu’s Donate link had to go. And, since updates are handled automatically in the background, the polite “Please donate!” link in the updater was effectively gone as well. So if I were to give away Paint.NET for free on the Windows Store, anyone who installed it from there would probably never even see the “tip jar” and be encouraged to contribute. So, I finally decided that I would just charge for the Store release. The Classic release will still be available and will continue to have a visible “tip jar” to encourage folks to provide financial support. And the Store release has some genuine advantages that you can pay for, if you choose. But what about plugins?! Oh! Don’t worry. Plugins are supported for the Store release. You just have to install them in a different location. Go to your Documents folder, create a folder called “paint.net App Files” (no quotes though), and then create a folder for each plugin type: Effects, FileTypes, and Shapes. And then put your plugins into each folder just like you’re used to with the Classic release. This does mean that plugins are installed per-user, mind you. This method of installation is also supported by the Classic release, by the way. If you’re a network administrator (or anyone really) who wants to disable this ability, you can do this with a registry key. In HKEY_LOCAL_MACHINE\Software\paint.net\, create a new string key called “Plugins/AllowLoadingPluginsFromUserLocations” (without the quotes) and set its value to “false”. Questions? Seriously, ask questions. This is a long blog post, but it’s new territory for myself and for Paint.NET and I probably missed something
  16. Did you just recently turn on the "show accent colors on: title bars" setting in Windows? If so, this will likely go away the next time you ... I think it goes away when you restart, or logout/login, or maybe even just when you restart the app. (I forget which). This isn't actually a new bug.
  17. I'm not adding a feature like that just because your PC is too slow. It's time to upgrade!
  18. v4.0.20 no silent install

    Silent install has never included the .NET installation. Nothing has changed with 4.0.20. You'll need to run the .NET installer by itself with its automatic settings, and then run the Paint.NET installer.
  19. paint.net 4.0.20 is now available!

    In order to move the control points on the line, you'll have to hold the mouse button down and then use the arrow keys. You can't just move the mouse cursor over to the control point.
  20. paint.net 4.0.20 is now available!

    What exact steps are you performing which causes this to happen? I'll have to keep iterating on this
  21. They (Microsoft) fixed this with .NET 4.7.1.
  22. Edge Blur RGB

    Actually, newer versions of Paint.NET, since 4.0, will handle an "unknown" blend mode just fine and revert the layer to Normal. I'm not sure how 3.5.x would handle it, but oh well. Can't always maintain forward compatibility.
  23. Edge Blur RGB

    It wouldn't break the PDN structure but older versions of the app wouldn't know what to do with it. It's just a big unknown right now.
  24. I've had some reports of this and it's something to do with the certificate not including (embedding) the chain of trusted parents up to the root certificate. It's not something I really understand and it only seems to affect things when the most stringent security checks are applied. The certificate itself is fine though, as far as I can tell. When it was reported to me it seemed to only be an issue on Linux or when using command-line tools (e.g. curl, wget), so I haven't really bothered with it. (esp. since I have absolutely no idea how to fix it)
  25. paint.net 4.0.20 beta build 6577

    Locking this since I'm releasing things.