Jump to content

Rick Brewster

Administrator
  • Content Count

    16,865
  • Joined

  • Last visited

  • Days Won

    159

Everything posted by Rick Brewster

  1. Alright, looks like this is just a corollary of the fact that PDN hasn't been upgraded to per-monitor (v2) DPI awareness. Implementing this has to come after porting to .NET Core, because it depends on new facilities added to WinForms in .NET Core 3 and 5. It's coming ... eventually
  2. Yeah I was only asking for diagnostic reasons -- I'm not suggesting you should or need to keep that configuration You may also check to see if you have any multimonitor- and/or window- management type of software installed. They often cause weird issues. ATI Hydravision for instance, is still bundled with AMD's Radeon drivers for some dumb reason, and same for NVIDIA equivalent with their Quadro drivers. Like c'mon, Windows has had that functionality built-in since Windows 98, or at least XP for sure ...
  3. Yeah if you have a Windows menu then you're probably using 3.5 (or even earlier). You need to install the latest version, which is currently 4.2.14.
  4. Does this happen if you set the two monitors to have the same DPI? (you'll need to exit the app before changing the DPI)
  5. Okay; I can put the property back with an [Obsolete] attribute
  6. Okay thanks for reporting that, I'll make sure it's fixed pronto
  7. This is on the (infinitely long) TODO list. For now, File->Exit followed by relaunching the app is the way to accomplish this. I've been hesitant to add this feature because it could be pretty easy to click on accidentally.
  8. If you want to do your own multithreading, specify RenderingSchedule = EffectRenderingSchedule.None when creating your EffectOptions in your constructor. Then your Render method will be called precisely 1 time and it will be given all of the ROIs (rectangle/region of interest).
  9. These are some popular fixes and additions 😁 Hopefully the alpha goes smoothly and a final release will be out soon!
  10. This is a small update that improves some quality-of-life issues, and fixes some important crashes due to mishandling of some non-fatal DirectX errors. To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app). You can also download and install this build directly: https://www.getpaint.net/files/zip/test/paint.net.4.215.7683.6519.install.zip Changes since 4.2.14:
  11. What, no? Use the Quick Access feature that's literally built-in to Windows. Look it up. Don't bump old threads like this. This thread is 14 years old! You risk being banned if you do this again -- please read the rules.
  12. I'm pretty sure all of that stuff already exists for iPad. Also, no, it's not happening.
  13. You can write a simple C# / LinqPad script to decode the thumbnail. base64 -> byte[], then wrap in a MemoryStream, then use Image.FromStream(). (it's just a PNG)
  14. Looks like Windows HEIC codec does not handle large images. What happens if you install @null54's Heic FileTypePlus plugin? Unfortunately I can't integrate this into the app because of HEVC's licensing and royalties. (HEIC is the container / file format, HEVC is the codec)
  15. This is possibly due to overzealous antivirus. In your cast, that's Avast. It's known to cause problems. You should uninstall it and just use Windows Defender, which is free and built-in to Windows.
  16. It's a long-standing issue that I just haven't addressed yet. It's more complicated than you'd think because the Shape rendering code has to handle floating point, not just integer, coordinates, as well as arbitrary 3x2 matrix transforms. Detecting that a pixel-aligned circle is being drawn isn't as straightforward as I'd hoped.
  17. 4.2.15 development is slow right now because of the holidays, I'm moving across the country soon, and I've just needed a bit of a break. An alpha should be coming soon. Just make sure to have "Also check for pre-release..." enabled in Settings -> Updates.
  18. Nope, not anything If the app boots up and works, repairing it should have no effect except in some ultra-rare (and only hypothetical so far) scenarios.
  19. This feature has been added for the 4.2.15 release. It's available on the Magic Wand, Paint Bucket, and Recolor tools.
  20. The "selection quality" (aliased vs. antialiased) affects how the selection is rendered, it doesn't change the selection itself. You can see the difference if you zoom in on a non-rectilinear/non-"pixelated" selection and toggle the toolbar button. Rectilinear means axis-aligned line segments, aka only up, down, left, right and only 90 degree angles. Pixelated is a PDN specific term (in the code, never seen in the UI) that means that all vertices are on integer (whole pixel) coordinates; it's a superset of rectilinear. In the code it's mostly used for a whole bunch of performance a
  21. I think Photoshop solves this by changing the mouse cursor to have an X, and if you try to click/draw on the layer it pops up an error. But, I'm with @Ego Eram Reputo on this: it's just part of the learning curve. It would require quite a bit of work to change this and there hasn't been many reports of this. It's certainly possible I just don't see it rising to the top of the priority list any time soon.
  22. Repair tool is only for fixing a broken installation. This is just something that doesn't work
  23. This is also not working for me ... I'll make sure it's fixed in the next update. Thanks for reporting this!
  24. The name of this folder is localized (translated), so that suggestion will only work for English. I would have them click on Open Palettes Folder and see how well that works. It will automatically create all the folders if possible:
×
×
  • Create New...