New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Does not work if the taskbar is moved to the top of the screen #6
Comments
Yeah, that is unfortunate. I came here for the same reason. Though, if the taskbar is at the top, could just set the position to a negative value instead of positive if the position is determined based on the taskbar itself being the origin? I have not looked over the code yet, so not sure, just a guess. |
Same here , would you please fix it for top taskbar users ? otherwise nice app ! |
Does not work with the taskbar on the side either. |
Should be an easy-ish fix, judging by Issue #2 - possibly just adapted presets for Top/bottom/left/right taskbars and mathematically reading the taskbar location |
This should be fixed in latest release 0.1.3 |
Good deal. It does seem to be working now. One thing I noticed though, if you click it then move the mouse away, the icons appear around wherever the mouse is after X amount of time. Not sure if that is intended? |
Thank you tjackenpacken for fixing that ! |
@mazenbesher I don't think that's intended behaviour, but a side-effect of how it makes the box appear - it calculates where your mouse is on the taskbar and draws the box right above it (this is because it isn't possible to read from Windows where something is pinned). Normally, it should appear instantly and you won't notice that. By the looks of it, if you're fast enough with the mouse, or your system is slow enough (e.g. high load) then the box can get drawn incorrectly. I tinkered with another C# program that draws boxes onscreen and it had a workaround by setting its own process priority to High. |
As Darthagnon mentioned this is not intended but it's hard to avoid. I'm gonna look over the priority if that could help. Since the initial issue has been resolved though the latest releases im closing this issue! |
No description provided.
The text was updated successfully, but these errors were encountered: