Everything
(context-menu) Path "expansions" is not always "expanded" when LFN are present
2 filenames
same path
2 SFN
or
1 filename
same path
1 LFN
if you right-click the Path (field), you're presented with the 'base directory path name'
& can then see the expected parent tree (from there)
---
2 filenames
same path
1 SFN, 1 LFN
or
2 filenames
same path
2 LFN
if you right-click the Path (field), you're presented with 'Parent Folders'
as if the 2 files were in different Paths (& you cannot then see the expected parent tree)
---
1. 1 LFN & Paths are present
2. 2 LFN & Paths are not shown - even though they're in the same directory
.
(context-menu) Path "expansions" is not always "expanded" when LFN are present
-
therube
- Posts: 5727
- Joined: Thu Sep 03, 2009 6:48 pm
(context-menu) Path "expansions" is not always "expanded" when LFN are present
You do not have the required permissions to view the files attached to this post.
-
void
- Developer
- Posts: 19903
- Joined: Fri Oct 16, 2009 11:31 pm
Re: (context-menu) Path "expansions" is not always "expanded" when LFN are present
Thank you for the issue report therube,
The next alpha update will show the correct BRU parent folder item, even when the file name is really long.
I will have an update soon.
The next alpha update will show the correct BRU parent folder item, even when the file name is really long.
I will have an update soon.
-
void
- Developer
- Posts: 19903
- Joined: Fri Oct 16, 2009 11:31 pm
Re: (context-menu) Path "expansions" is not always "expanded" when LFN are present
Everything 1.5.0.1384a will now show the single Parent folder menu item when all the parent folders are the same and there's a very long filename.