You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
The restore option and Log Window option of context menu in taskbar shows the window in taskbar, but it's completely invisible and not shown anywhere on screen.
Hovering over it shows it's blank-white. And windows keys to move to another monitor do nothing to absolve the issue.
It works fine for existing connections, but you can't add new ones due to this.
The text was updated successfully, but these errors were encountered:
Do you face this problem after first installation or upgrade or it appears later after some time? After applying your workaround mentioned above the issue appears again? Do you change monitor configuration? What version of system?
I believe this is caused by having 2+ monitors on the host machine, then removing the monitor physically.
It stores the "last known position" on exit, resulting in negative or far-excessive values.
Should be a rare edge case. But figured I'd mention it.
However ideally on loadup the gui app would detect out-of-range values in registry and reset it to [0,0] as a preventative maintenance.
Definitely low priority, and potentially on the [feature request] layer of things.
Latest version.
The restore option and Log Window option of context menu in taskbar shows the window in taskbar, but it's completely invisible and not shown anywhere on screen.
Hovering over it shows it's blank-white. And windows keys to move to another monitor do nothing to absolve the issue.
It works fine for existing connections, but you can't add new ones due to this.
The text was updated successfully, but these errors were encountered: