This issue may be functionally related to #1 from this post (#ODNT-9817), but presents differently.
System
When the taskbar is on the bottom of the screen, desktop icon grid snapping is as expected, in that you need to move an icon roughly the same distance up or down to get it to move the next spot above or below its current position. There is a slight bias towards moving the icon down, and I haven't tested the distances with the vanilla taskbar (i.e. Start11 disabled) to see if the distances are exactly equidistant there, but with the Start11 taskbar on the bottom the movement thresholds feel more-or-less correct (though just be advised that there could be a slight discrepancy compared to stock Windows, even when the taskbar is on the bottom, since again I haven't compared directly).
The issue, is that when the taskbar is switched to the top, for whatever reason the thresholds for snapping to the next spot in the grid completely change and become massively biased towards an icon moving up; that is, the icon has to be moved ridiculously far down for it to go to the lower spot, and only a smidge upwards for it to move to the higher spot.
I tried to tease out the exact point past where the icon would actually move for each position of the taskbar as best I could in order to create the following visual that summarizes the problem.
This is at 100% desktop scaling and of course the pixel counts vary depending on monitor size and whatever icon size I'm using, but its just to get the point across.
Hello,Sorry to hear you are having issues. I can not reproduce you observation on my system. However, I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.
Thank you,Basj,Stardock Community Assistant.
Thanks for bringing this to their attention.
Just curious, did you test with the taskbar on top AND Start11 autohide enabled? Although I showed I have autohide turned on in my system configuration section, I did not highlight that in my post body. I just tried this out in a relatively fresh VM and was able to confirm that the issue does not present from simply having the taskbar on top, but rather having it on top AND with autohide enabled (as well as confirming that it occurs on another system period).
I have updated the post title to reflect this fact.
I retested with Start11 taskbar autohide enable, but I still can not see it. Hopefully Support can see it.
Thank you,
Basj,Stardock Community Assistant
Hi oblivioncth,
Thanks for posting. I was able to reproduce this in a Windows 24H2 Sandbox.
I followed these steps:
If the taskbar autohide is turned off, the problem stops reproducing. If autohide is kept on and the taskbar is moved back to the default bottom position, the problem also will stop reproducing.
This will be logged for internal review
Internal Ref: ODNT-9895
Best regards,
Adam McGuinnessStardock Customer Support Specialist
Thanks Adam,
That all sounds like it matches my experience to me.
There are many great features available to you once you register, including:
Sign in or Create Account