[VB6] Class: PathLinks - Tame App.Path Under Vista+

[dilettante]

I've been wavering on whether to post a corrected version that addresses a couple of bugs. I'm beginning to wonder if it wouldn't be better just to create a 2.0 version that uses CommonAppData and sets the ACL instead of this approach that uses Public.

Since people have looked at what I've posted so far though, it seems only right to put a version correcting some bugs here first.

The biggest flaw in the earlier versions was that it left current directory set wrong even though I had meant to reset it to its original value. That won't happen anymore.


When looking at the demo project, note that the entire "application" is in the Form1 code. Everything else is meant to (a.) set up Common Controls 6.x, (b.) provide Task Dialogs in Vista or later, and (c.) do this "PathLinks" thing.

Version 1.2 above left out Task Dialog support, so it might be simpler to look at even though it still has the current directory bug.

If you want to use 1.3 without Task Dialogs, just change the call to STDlg.TaskDialog() to a MsgBox() call instead. Then remove the STDlg.cls module since you won't be using it anymore. MsgBox() dialogs just look sort of old-timey and Win 3.1-ish on newer versions of Windows.


Using Public instead of CommonAppData did two things: (1.) unlike CommonAppData, Public files and folders aren't hidden which some people see as a bonus; (2.) since Public files and folders don't default to "owner" security unlike CommonAppData, they provide a read/write location for all files and users without the need to alter the security ACL on them.

The second reason was the big one, but a CommonAppData version of PathLinks could handle that.