libiomjobs

libiomjobs

Joined Last seen Member # 7544221
0 Posts 10 Replies 80 Reputation

Thank you, Basj, for testing it out. I'm posting a video per your request, but first I do want to point that in your video the issue does appear, briefly, between the 7- and 8-second marks. When you switch over to the desktop with Settings and you move the pointer around at the bottom, for a moment the pointer changes to a vertical resize tool (double-headed arrow up-down) for no reason. You'll see it in my video below as well, but I thought it prudent to point it out. In my video bel

28 Replies 6,957 Views

I am experiencing this same behavior in Version 2.6. Windows Taskbar hide option is turned off, Reserve 1 Pixel option is turned on (though I've tried it both ways). If I force it to show by hovering the cursor at the bottom, and then let it auto-hide again, it no longer interferes. Switching desktops (Win+Ctrl+Right/Left) while it's hidden seems to cause it to "appear" invisibly. There may be other triggers, but that one is consistent.

28 Replies 6,957 Views

The issue has returned. Secondary monitor, snap a window to maximize or one of the lower standard Windows 11 zones, and the bottom of the screen appears to reserve space for the (hidden) taskbar. If I switch the "Reserve one pixel..." option off and then back on, the window snaps all the way to the bottom as expected (no need to restart Explorer). Thoughts?

24 Replies 17,419 Views

Edited my previous reply, but I'll formalize in a new reply. It appears v2.55 does not display the issue, so it may be resolved. As for leaving the "Reserve one pixel..." option off, I have found that that results in some other weird behavior, such as the "snap edges" not being detected when I try to drag windows to maximize.

24 Replies 17,419 Views

Reboot doesn't resolve the issue. In fact, the issue returns each time I reboot. The only workaround I've found is to turn off "Reserve one pixel" and then turn it back on. I have to do this every time I reboot. *edit* I'm updating now; will advise if the issue remains. After update, v2.55 does not appear to display this behavior. If it crops up again I'll resurrect the thread.

24 Replies 17,419 Views