-
-
Notifications
You must be signed in to change notification settings - Fork 416
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
Persistent taskbar NotifyIcon in top left corner #793
Comments
I came to report the same issue. Although for me it's not limited to a multi-monitor setup. OS: Win 11 / Win 10 On my (single-monitor) Win 11 machine, whenever I move the mouse cursor across the system tray area there is a fifty-fifty chance that the simple NotifyIcon pops up in the very top left corner. I do have the same issue on a Win 10 machine too although on that machine it happens quite rarely. I can still reproduce it reliably if hover my mouse around the tray icon for a while. But it's more like a 10% chance and rarely happens in everyday practice. What is expected behavior: Actual behavior: Thoughts: We're using the Hardcodet.Wpf.TaskbarNotification library version 1.0.8 for the popup, which was last updated in 2016 - seems to be abandoned by the original dev. @C0gwh33l maybe you want to generalize the title to something like: "Persistent taskbar NotifyIcon in top left corner" |
changed title to reflect issue, and as documented above the issue is the same, regardless of monitor amount on a sole laptop this is reproduced aswell |
I have the same problem +1 |
OS : Win 11
Version latest to date : 1.1.29
Issue im dealing with is whenever a multimonitor (laptop + primary monitor) is being used the upper left corner of my primary monitor gets a SyncTrayzor howerover trayicon that is persistent of wether i mouseover it on the left upper corner and leaves only if moused over on the taskbar, i have yet to confirm wether this is an issue with returning from hibernation but it seems to be specifically aimed at SyncTrayzor
The text was updated successfully, but these errors were encountered: