Bugs: Fences renaming documents in fences, not moving icons properly

Latest version

from Stardock Forums

My system is running Windows 10 Enterprise, 1703, and I'm encountering two bugs in the latest version of Fences.

 

One is that Fences is arbitrarily renaming the titles of some select documents that I have organized in fences, and which I access frequently. The title change is only for the icon description, as when I open the document, the title within Microsoft Word is the proper title. The renamed title is as the name of another icon on my desktop, like it just copied the name from another folder which I have pictures in.

I renamed the document once before, after its icon title changed. Now, it has changed again, to the same title as another desktop item.

Again, as I said, the name of the document only changed for its desktop icon, while its title when open in Microsoft Word remained as I had originally titled it.

I have only seen this behaviour happen to items that I have grouped in fences.

 

 

The other bug that I'm encountering with Fences enabled is that icons don't always move to where I drag them to move. Sometimes they shoot off in a different direction, and sometimes they just refuse to move into the desktop spot that I drag them to.

Here is a video I made showing it happening.

 https://youtu.be/UPiGp55WQz4

Towards the end of the video, you can see that I select two icons and drag them together, and then when I let go of the mouse button, the icons shoot off in different directions.

fences
20,782 views 8 replies
Reply #1 from Stardock Forums Top

By the way, I am using 1440p resolution, and have 3 desktop pages with these settings:

 

Reply #2 from Stardock Forums Top

I reported the same behavior in Fences 3.0 a couple of months ago, was given instructions on how to clean-reinstall Fences.  I run a multi-monitor portrait configuration, and frequently see shortcuts renamed and moving to wherever they want outside of their assigned fence.

Given the support response I saw on that ticket, and the 3-month old unresolved bug from another ticket I have going, I'm not confident about support's ability to resolve these things.

I wish you luck in finding a resolution.   I've let my Object Desktop subscription lapse, and don't have plans to renew it based on what I've seen from support.

Siege of Centauri
Reply #3 from Stardock Forums Top


One is that Fences is arbitrarily renaming the titles of some select documents that I have organized in fences, and which I access frequently.
End of quote

That was resolved with 3.05 - it mainly affected MS Office files as they create temps.

Reply #4 from Stardock Forums Top

Just FYI - Fences is still doing this, albeit infrequently.  Did it to one of my .exe shortcuts which resided in a standard Fence this morning.  The name was taken from a .txt file on the Desktop and the .exe's shortcut renamed with it.  It happens to me about once a month, usually right after I've created a new file and placed it on the Desktop.  Seems to happen right at boot time.  Definitely not resolved.

 

The shortcut to the right (in the Fence) was originally named "Windows Borderless Gaming".  The "OP.txt" file resides on the Desktop, not in a Fence, and is new as of yesterday. 

Edit:  Fences is still auto-ejecting certain shortcuts from user-created fences, it just happened to the OP shortcut in the fence image above.  It pushed the shortcut back to the Desktop, out of it's assigned Fence.

Reply #6 from Stardock Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.
Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #7 from Stardock Forums Top

I believe the issue was fixed. I have not seen the problem again after my last update. I am at V3.0.8.1.

Reply #8 from Stardock Forums Top

Maybe the naming issue is fixed, I don't know. But, from what I recall, I was still having the issue with desktop icons not moving properly the last time I was using Fences, which was about 1 month ago. I'm not sure what version of Fences 3 I was on then, but I think I had it set to auto-update.

I haven't yet installed Fences on my new installation of Windows 10 due to multiple serious bugs that haven't been fixed despite being reported long ago. This issue being one of them.