Page 2 of 4
Re: Better handling of junctions
Posted: 06 Dec 2011 12:21
by admin
Well, OK, I could convert "C:\Documents and Settings\Don\Anwendungsdaten\Dropbox" into "C:\Users\Don\AppData\Roaming\Dropbox" before feeding it to the tree, and then silently change the AddressBar contents (if it was pasted there) to the converted path. Hmm, is that good?
Re: Better handling of junctions
Posted: 06 Dec 2011 12:54
by Marco
admin wrote:Well, OK, I could convert "C:\Documents and Settings\Don\Anwendungsdaten\Dropbox" into "C:\Users\Don\AppData\Roaming\Dropbox" before feeding it to the tree, and then silently change the AddressBar contents (if it was pasted there) to the converted path. Hmm, is that good?
It could be a nice addition.
In the meantime I've modified my habits so to include more relative paths, and the need for "resolvable junctions" has almost gone.
Don, it's up to you
By the way, I confirm that locking the tree as you suggested works as expected (using 10.60.0113)
Re: Better handling of junctions
Posted: 06 Dec 2011 12:55
by nas8e9
admin wrote:Well, OK, I could convert "C:\Documents and Settings\Don\Anwendungsdaten\Dropbox" into "C:\Users\Don\AppData\Roaming\Dropbox" before feeding it to the tree, and then silently change the AddressBar contents (if it was pasted there) to the converted path. Hmm, is that good?
Sounds good to me, especially as with locking the Tree, the List doesn't resolve to the physical path (should have noted that in my previous post) but remains "hanging" under the junction (should be C:\Users\[username]AppData\Roaming but with locked Tree remains in C:\Documents and Settings\[username]\).
Re: Better handling of junctions
Posted: 06 Dec 2011 21:28
by admin
I'll experimentally add something to the next beta...
Re: Better handling of junctions
Posted: 07 Dec 2011 14:34
by nas8e9
The ResolveNestedJunctions=1-tweak works for me so far. Thank you!
Re: Better handling of junctions
Posted: 09 Dec 2011 20:08
by admin
admin wrote:I'll experimentally add something to the next beta...
Marco, speak to me...
Re: Better handling of junctions
Posted: 09 Dec 2011 23:08
by Marco
admin wrote:Marco, speak to me...
Works perfectly here! [Win 7 Italian]
I tried different "junctioned" paths and I found no problem so far.
Re: Better handling of junctions
Posted: 10 Dec 2011 09:34
by admin
Marco wrote:admin wrote:Marco, speak to me...
Works perfectly here! [Win 7 Italian]
I tried different "junctioned" paths and I found no problem so far.
Good! I wonder if this tweak should become the factory default... hmmm...?
Re: Better handling of junctions
Posted: 10 Dec 2011 10:20
by Marco
In my opinion, it would make sense.
Re: Better handling of junctions
Posted: 18 Dec 2011 19:21
by Marco
Here we go again
I'm playing with junctions (of course) and I notice a different behaviour between XY on XP and XY on 7. Let's paste a path with a junction in XY address bar.
7: the path is fully "parsed" (can't think of a better term), so that it contains no junctions in it; it is a real/physical path.
XP: the path preserves the junctions in it; the end result is a mix of real and "virtual/junctioned" parts.
I'd like to know if anybody can confirm this behaviour and would like to receive some insight. By doing some trials seems that this behaviour is related to XY itself and not the underlying OS.
Re: Better handling of junctions
Posted: 19 Dec 2011 10:42
by admin
Marco wrote:Here we go again
I'm playing with junctions (of course) and I notice a different behaviour between XY on XP and XY on 7. Let's paste a path with a junction in XY address bar.
7: the path is fully "parsed" (can't think of a better term), so that it contains no junctions in it; it is a real/physical path.
XP: the path preserves the junctions in it; the end result is a mix of real and "virtual/junctioned" parts.
I'd like to know if anybody can confirm this behaviour and would like to receive some insight. By doing some trials seems that this behaviour is related to XY itself and not the underlying OS.
Well, I made it apply only to Win7!

I did not expect anybody in XP needed this junction stuff since only Win7 introduced the junction hell to the innocent users. I will change it, no problem...
Re: Better handling of junctions
Posted: 19 Dec 2011 15:34
by Marco
Wait a second: I fully understand that the tweak you introduced in this thread only applies to vista and 7.
What I noticed is a strangely different behaviour: feeding a path with junctions inside XY address bar on XP gets me to destination! It doesn't stop half way as 7 did.
That's what baffles me...
Re: Better handling of junctions
Posted: 19 Dec 2011 20:32
by admin
Marco wrote:Wait a second: I fully understand that the tweak you introduced in this thread only applies to vista and 7.
What I noticed is a strangely different behaviour: feeding a path with junctions inside XY address bar on XP gets me to destination! It doesn't stop half way as 7 did.
That's what baffles me...
Hm, that's indeed baffling. So I should not change the tweak to apply to XP also? Hard to say without fully understanding what's going on... for now I will change it. You and nas8e9 are probably the only persons using the tweak anyway

Re: Better handling of junctions
Posted: 19 Dec 2011 21:18
by Marco

I'm so sorry to bug you again but it looks like the tweak doesn't work with junctions pointing to volumes different from the system one.
I have the the junction
C:\Dati pointing to the volume
N:\. When I try to go to
C:\Dati\Marco (via catalog) I'd expect to end in
N:\Marco, yet the address bar shows
N:\\Marco (extra slash), and the according location currently not available error.
All the other junctions (intra-volume) work fine.
Re: Better handling of junctions
Posted: 20 Dec 2011 09:26
by admin
Marco wrote:
I'm so sorry to bug you again but it looks like the tweak doesn't work with junctions pointing to volumes different from the system one.
I have the the junction
C:\Dati pointing to the volume
N:\. When I try to go to
C:\Dati\Marco (via catalog) I'd expect to end in
N:\Marco, yet the address bar shows
N:\\Marco (extra slash), and the according location currently not available error.
All the other junctions (intra-volume) work fine.
Confirmed and fixed.
I also confirm that in XP the tweak does not seem necessary.