ikjadoon Posted January 16, 2021 Share Posted January 16, 2021 (edited) Paint.NET: version 4.2.14 (final 4.214.7601.39231) OS: Windows 10 Pro x64 20H2 (19042.746) Display 1: 2560x1440 @ 125% DPI / Intel i5-8600K iGPU, driver 27.20.100.9126 Display 2: 1920x1080 @ 100% DPI / NVIDIA GT 710 dGPU, driver 27.21.14.6109 (problem occurs only on this monitor) What should happen: when Paint.NET is maximized, its window should extend to the top of the monitor. So, moving your cursor to the top-right should always hit the red "X" close button. What actually happens: Paint.NET leaves an unusual gap at the top and I often click the window behind Paint.NET when Paint.NET is in fact maximized. This 1px gap is not consistent, but is sometimes there and sometimes not. The easiest way to show this is 1) open Paint.NET on a 2nd monitor, 2) maximize Paint.NET, 3) run your mouse at the top-right of your window. Google Chrome Maximized (version 87.0.4280.141) Paint.NET Maximized (version 4.2.14) In some regions, Paint.NET is now hovering over the program behind it and thus you end up misclicking. This bug is not an animation bug; when Paint.NET loses focus in the animation, so has your mouse. The flickers are when you're hovering over the window behind Paint.NET. This bug also occurs with NotePad++ (someone reported it in August 2020), so I wonder if there's a framework or library that's the same between the two applications. Edited January 16, 2021 by ikjadoon added in GPU & driver info, per monitor Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 17, 2021 Share Posted January 17, 2021 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) 1 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...
Ego Eram Reputo Posted January 17, 2021 Share Posted January 17, 2021 I'm not seeing this on my dual-monitor system. 1 Quote ebook: Mastering Paint.NET | resources: Plugin Index | Stereogram Tut | proud supporter of Codelab plugins: EER's Plugin Pack | Planetoid | StickMan | WhichSymbol+ | Dr Scott's Markup Renderer | CSV Filetype | dwarf horde plugins: Plugin Browser | ShapeMaker Link to comment Share on other sites More sharing options...
ikjadoon Posted January 17, 2021 Author Share Posted January 17, 2021 (edited) On 1/16/2021 at 8:24 PM, Rick Brewster said: 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) Ah, hello! Thank you so much for developing Paint.NET. It's saved my life many times; I've bought the Store version, but prefer the *.exe for some flexibility purposes. Thank you. And you're exactly right. With more DPI testing & switched around the monitors, the bug only reproduces 1) if the DPIs are not equal and 2) on the secondary monitor. Monitor 1 (primary) : 1440p @ 125% DPI Monitor 2: 1080p @ 100% DPI (bug appears here) Monitor 1 (primary) : 1440p @ 100% DPI Monitor 2: 1080p @ 125% DPI (bug appears here) Monitor 1 : 1440p @ 125% DPI (bug appears here) Monitor 2 (primary) 1080p @ 100% DPI Monitor 1: 1440p @ 100% DPI (bug appears here) Monitor 2 (primary) : 1080p @ 125% DPI Unfortunately, I'm at 125% and 100% DPI (the recommended DPI by Windows for the 1440p & 1080p displays, respectively). I understand if this bug is a corner case, low-hit-rate by Paint.NET users. It's not a serious bug, but perhaps noted for the future, as seemingly all of my other applications (except notably Notepad++) don't exhibit the bug on split-DPI configurations. On 1/16/2021 at 10:10 PM, Ego Eram Reputo said: I'm not seeing this on my dual-monitor system. Ah, fair. Are you running two different DPIs? Edited January 18, 2021 by ikjadoon Quote Link to comment Share on other sites More sharing options...
Ego Eram Reputo Posted January 18, 2021 Share Posted January 18, 2021 2 hours ago, ikjadoon said: Ah, fair. Are you running two different DPIs? No, the same DPI. I think your post above confirms the issue is with different DPI settings. 1 Quote ebook: Mastering Paint.NET | resources: Plugin Index | Stereogram Tut | proud supporter of Codelab plugins: EER's Plugin Pack | Planetoid | StickMan | WhichSymbol+ | Dr Scott's Markup Renderer | CSV Filetype | dwarf horde plugins: Plugin Browser | ShapeMaker Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 18, 2021 Share Posted January 18, 2021 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 ... 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...
ikjadoon Posted January 18, 2021 Author Share Posted January 18, 2021 (edited) No, none at all: agreed, Windows does it more than well enough. I'd consciously avoid windows (lowercase 'w') management software just for that reason: I'm already feeling anxious just thinking of how many programs don't play well. On the NVIDIA GT 710 (not Quadro), it's just the NVIDIA drivers: I long uninstalled their GeForce Experience bloatware. // However, it does look like it's something much deeper than Paint.NET. I ran through my programs list and found these applications exhibited the bug: Notepad++ 32-bit 7.9.1 Paint.NET 4.2.14 7-zip x64 19.00 Most Adobe CC software (latest) Apple iTunes 12.11.0.26 (does not exhibit hover symptom, but still can click behind) These programs did not exhibit the bug: Chrome 87.0.4280.141 All Office applications (latest) Adobe Illustrator CC (latest; 25.1) Audacity 2.4.2 Noting your DPI test, I used Task Manager's DPI Awareness. The bug almost always appears in programs with "DPI Awareness = System". The safe applications are set to "DPI Awareness = Unaware" or "DPI Awareness = Per-Monitor (v2)" like Chrome, which is a mix of unaware and per-monitor v2. I'll run some more tests and see what can be done. But, yes: I think this bug report can be closed on Paint.NET's end as it's not just Paint.NET & Notepad++, but a whole bevy of applications. Though half of me thinks that it's time to upgrade to 2x 1440p monitors, haha... Edited January 18, 2021 by ikjadoon Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 18, 2021 Share Posted January 18, 2021 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 1 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...
ikjadoon Posted January 22, 2021 Author Share Posted January 22, 2021 (edited) Thank you kindly for the update. No worries: take your time. Paint.NET is certainly not the only application with those updates in the backlog. Thank you for having it on your radar. In the mean time, I've changed to 2x 1440p monitors to avoid this issue (and others!), so I'm good on this front as well. Thank you again for your thoughtful replies & candid efforts. I'm off to more excellent editing 😎 Edited March 19, 2021 by ikjadoon typo 1 Quote 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.