srwi / EverythingToolbar

Everything integration for the Windows taskbar.
Other
9.49k stars 412 forks source link

Bug: Explorer crashes when attempting to use toolbar icon in a position where taskbar is not horizontal on a secondary display #329

Closed ThePerfectLink closed 1 year ago

ThePerfectLink commented 1 year ago

Preflight Checklist

EverythingToolbar Version

1.0.2

Windows Version

Windows 10 Pro V. 21H2

Steps to reproduce

  1. Have multiple monitors
  2. go to taskbar settings
  3. turn off "show taskbars on all displays"
  4. unlock taskbar
  5. reposition taskbar to secondary monitor in a vertical position against side furthest from main display
  6. click on search everything toolbar
  7. watch your explorer explode

Expected Behavior

It's supposed to open next to the taskbar I imagine

Actual Behavior

It attempts to open on the main monitor, fails and crashes explorer

Screenshots

No response

Log output

2023-02-09 10:25:52.6563|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:25:52.6613|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:25:58.6931|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.1.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:26:20.6156|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:26:20.6156|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:26:22.6312|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.1.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:26:28.7843|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:26:28.7843|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:26:51.5360|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.1.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:26:57.3668|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:26:57.3668|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:26:59.4638|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.1.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:27:06.4508|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:27:06.4508|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:47:19.4123|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.2.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:47:32.5805|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:47:32.5805|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:47:41.9772|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.2.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:50:11.3243|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:50:11.3243|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:50:16.7579|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.2.0 started. OS: Microsoft Windows NT 10.0.19044.0| 2023-02-09 10:54:08.2144|ERROR|EverythingToolbar.EverythingSearch|IPC is not available.| 2023-02-09 10:54:08.2144|ERROR|EverythingToolbar.EverythingSearch|Failed to get Everything version number. Is Everything running?| 2023-02-09 10:54:10.1151|INFO|CSDeskBand.CSDeskBandWpf|EverythingToolbar Deskband 1.0.2.0 started. OS: Microsoft Windows NT 10.0.19044.0|

Additional Information

Also when you put the taskbar in a position that is touching the main monitor on a monitor that isn't your main one and attempt to open the taskbar widget it opens it on the main monitor rather than under or over the icon.

srwi commented 1 year ago

Hi @ThePerfectLink, sorry for the late response and thanks a lot for the detailed bug report. A fix for the bug will be available in the next release!