Fences doesn't seem to respect my default handler for folder shortcuts

Fences always uses Windows Explorer for folder shortcuts

from Stardock Forums

I use Directory Opus (DO) a lot because it's arguably the best file manager for Windows. I much prefer it to Windows Explorer, which is why I've configured it as the default handler for folders and their shortcuts. So if I place a shortcut to a particular folder on my desktop and double-click it, it opens in DO and not Windows Explorer.

When I drag the very same shortcut into a fence and double-click it there, however, it opens in Windows Explorer. It doesn't seem that Fences respects the system default handler for folder shortcuts. Can you fix this? Or at least tell me how to work around it? It's a deal-breaker for me using folder shortcuts with Fences.

fences
11,704 views 9 replies
Reply #1 from Stardock Forums Top

Hello,
I have forward 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.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

Fences runs in the Windows explorer process and it defaults to that.  No other shells are currently supported but I will pass on your observations.

Sean Drohan
Stardock Support Manager

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top

To be clear, I'm not running any "other shell", I'm simply asking that Fences respect the default system settings for what application opens for folder shortcuts. That's got nothing to do with the "shell", insofar as I too am running Windows Explorer as the system shell.

Reply #4 from Stardock Forums Top

Quoting Phileosophos, reply 3

To be clear, I'm not running any "other shell", I'm simply asking that Fences respect the default system settings for what application opens for folder shortcuts. That's got nothing to do with the "shell", insofar as I too am running Windows Explorer as the system shell.
End of Phileosophos's quote

Noted, thank you for the clarification, one I will pass along as well.

Sean Drohan
Stardock Support Manager

Reply #5 from Stardock Forums Top

Another clarification after more testing: the shortcuts work fine in a regular fence (i.e., opening in Directory Opus as they should) but fail only when they are part of a "folder portal", which is what I have been using for convenience. The problem seems confined to folder portals, so perhaps there's something you can look at specific to that code? In the meantime, I have a workaround.

Reply #6 from Stardock Forums Top

Quoting Phileosophos, reply 5

Another clarification after more testing: the shortcuts work fine in a regular fence (i.e., opening in Directory Opus as they should) but fail only when they are part of a "folder portal", which is what I have been using for convenience. The problem seems confined to folder portals, so perhaps there's something you can look at specific to that code? In the meantime, I have a workaround.
End of Phileosophos's quote

Folder portals actually use Windows Explorer and likely the reason why.  If possible, you might try a right-click and see if there is an 'open with' option.

Sean Drohan
Stardock Support Manager 

Reply #7 from Stardock Forums Top

There is just such an option, but that's doubly weird insofar as I've since learned two things:

  1. I can't get folder navigation to work in folder portals at all. It simply opens the folder in an external Windows Explorer window.
  2. Yet double clicking empty space in the folder portal or the title bar correctly opens the folder in Directory Opus!

To call this schizophrenic behavior would be an understatement...

Reply #8 from Stardock Forums Top

While we really don't account for another file manager with Fences...

Quoting Phileosophos, reply 7

I can't get folder navigation to work in folder portals at all. It simply opens the folder in an external Windows Explorer window.
End of Phileosophos's quote

Check:

Sean Drohan
Stardock Support Manager

Reply #9 from Stardock Forums Top

Sorry, I should have been more explicit: it's already checked. That's what makes it so frustrating.