Poor Multiple Monitor Support

[GoogleCodeExporter]

What version of the product are you using? On what operating system?
1.1.1.0 on Windows 7 64-bit.

Please provide any additional information below.
Full Screen Color Picker does not work properly on 2nd and 3rd monitors.

Original issue reported on code.google.com by [email protected] on 16 Aug 2013 at 4:59

[GoogleCodeExporter]

Have you tried to move np++ to target screen and pick?

The full screen color picker is designed to pick color from the screen where 
np++ is in.

I may add multi-screen support when I got time.

Original comment by [email protected] on 22 Aug 2013 at 2:04

[GoogleCodeExporter]

It only works properly if used on the 1st monitor. If np++ is opened on (or 
moved to) the 2nd or 3rd monitor, and you open the Full Screen Color Picker, 
the "Zoomed Aim" window will appear on the 1st monitor (or very far to the 
left of the 2nd monitor), even though the eyedropper selector is on the 
other monitors. There is a very large horizontal shift between the 
eyedropper and the "Zoomed Aim" window.

I guess the workaround for now is to simply move np++ to the 1st monitor to 
use this feature.

Original comment by [email protected] on 22 Aug 2013 at 5:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'll check it out.

But first, I need to get another monitor.

Original comment by [email protected] on 23 Aug 2013 at 1:54

[GoogleCodeExporter]

Original comment by [email protected] on 23 Aug 2013 at 1:54

• Changed state: Accepted

[CollinChaffin]

Wow this is the FIRST bug ever reported YEARS ago and it's what I just came to report. Hope just sunk in my stomach of seeing this fixed anytime soon, LOL.

It's not an enhancement, at least tag it correctly for gosh sake. If you move NPP to any monitor other than primary this plugin is the ONLY one who's corresponding popup window instead of normally popping up nicely at the color code being double-clicked, now opens on the next monitor over eight-miles away, like a drunken sailor, LOL. I'd recommend perhaps classifying as a BUG. :)

I love this plugin so I too really hope you can get around to maybe fixing this bug that makes it VERY difficult to even use.

[CollinChaffin]

FYI, last coding/commit activity at all from the owner of this repo was July of 2016. He's shown up to just blatantly close issues for some reason he is refusing to fix, so I would recommend just forking this yourself as it does not appear to have any active development.