Desktop auto-icon-spacing previously broken, now finally fixed

Hello, We’re sorry to hear about your frustration with Fences and truly appreciate you sharing your experience.

It would help us a lot if you could provide more details about the auto-icon-spacing issue you’re seeing in Fences 6, so our team can investigate further. While we understand your disappointment, your feedback is valuable in helping us improve.

You may also want to check this related discussion: https://forums.stardock.com/541293. As you’ll see, the lead developer is actively engaging with users on this topic. Since we haven’t received many recent reports about this issue, your input there could be especially helpful.

We hope you’ll reconsider and give us the chance to work with you on resolving this. Thank you again for taking the time to share your thoughts.

Basj,
Stardock Community Assistant.

? Can you share a link to the original post please.

A debug log which contains extensive information about icon spacing can be made by

(1) About -> Troubleshooting -> Enable advanced debug log

(2) Log off / on, recreate the issue

(3) Upload to the team via About -> Troubleshooting -> Create Error Log Package

This will allow the team to see more about what is going on. Thank you

Are you serious with your debug log crap? It is a very-well documented issue that happens on absolutely all machines running all fresh installs of Windows 11, so nothing related to a particular setup. Therefore a debug log won't change anything, it is the programming staff's job to test it and figure it out, not ours. 

We are not reproducing the issue. There are a handful of users who are reporting this. There are >100,000 active licensed copies of Fences. If it happened to everyone as you state there would be many hundreds of posts.

I should add that spacing, when you change between DPIs and monitors, is something that Windows itself handles in an inconsistent manner. Considerable work has been done to de-“mess-up” the spacing readings it provides when going between DPI states. It is most likely to occur after the system changes DPI from its boot up state.

It is interesting the claim is that we could care less, while at the same time we have built systems to help collect information, and are on here helping individuals on a one by one basis / are offering to do so with you today.

Finally fixed in 6.52:

"Fixed overlapping icon spacing issue when icons are in "Large" mode."
https://forums.stardock.com/542120/fences-6-52-release-feedback/page/1#3996504

Better late than never, I guess.

This issue had a huge longevity. It was introduced in Stardock 4 then never fixed, then Stardock 5 didn't make it any better. Honestly I'm glad it has been solved at last... after more than 4 years...

Hi filouk

Understandable. This was an issue that more or less was a “can’t 'fix’ per-se without breaking it for many others” situation, and there were several attempts made to improve the algorithm over the years with varying degrees of success. Ultimately, we’re a dance partner with Explorer, and must precisely read its metrics & behavioral cues on all OS versions and in all conditions through all manners of system state. This was a tricky one and we’re glad that we’ve seemingly finally gotten all the cases solved 🙌

Feedback welcome on other areas of the app to improve, shortcomings, new features to suggest etc. While the subscription approach and new pricing over the last couple years have been somewhat unwelcome, it has enabled us to be much more proactive in our ongoing improvements, with a focus first of ensuring we don’t introduce problems (march reliability forward as priority #1) over jamming in new features, with finding good ways to keep improving. We tend to introduce new functionality ~annually while continuing to patch issues and provide more minor ongoing improvements to the core of the app for old versions v5 and onward.

Appreciate again your having stuck around

❤️ Thank you very much for taking the time to answer. Glad it could be sorted out and sorry for the previous "tone", well I didn't cancel subscription anyway, for that matter 😉.

Best.