[Bug] Popup positioning under windows
Posted: Sat Jun 22, 2019 1:26 pm
This may seem like a pretty minor thing, but believe me its actually really annoying .
In my setup (Windows 7) I have two monitors side by side, the right monitor is my primary monitor and has the taskbar on the left side.
So from a logical perspective you could say that the taskbar is between my two monitors.
Now "normal" windows behavior is that when you open a tooltip on one monitor it stays on that monitor (for obvious reasons). And that is true for all other programs on my pc and in my taskbar.
But Viscosity is doing something strange (I guess you handle the tooltip displaying yourself or something):
When I right-click on the traybar icon the tooltip is opened left facing on the right side of the other (the left) monitor.
This always results in a second of fumbling with the mouse when moving from one monitor to another near their edge, especially because I have two different monitor models and they don't align perfectly...
As I said its not really a bug in the core functionality but I have the hope that it should be a pretty quick fix and perhaps someone can take the time to look into it...
Regards
Mike
In my setup (Windows 7) I have two monitors side by side, the right monitor is my primary monitor and has the taskbar on the left side.
So from a logical perspective you could say that the taskbar is between my two monitors.
Now "normal" windows behavior is that when you open a tooltip on one monitor it stays on that monitor (for obvious reasons). And that is true for all other programs on my pc and in my taskbar.
But Viscosity is doing something strange (I guess you handle the tooltip displaying yourself or something):
When I right-click on the traybar icon the tooltip is opened left facing on the right side of the other (the left) monitor.
This always results in a second of fumbling with the mouse when moving from one monitor to another near their edge, especially because I have two different monitor models and they don't align perfectly...
As I said its not really a bug in the core functionality but I have the hope that it should be a pretty quick fix and perhaps someone can take the time to look into it...
Regards
Mike