How to repeat this bug or [in other words] an-illogical-user-unfriendly-behavior:
1] Create in the same folder four folders named
TEST-1
TEST-2
TEST-3
TEST-4
2] Place folder TEST-2 in folder TEST-1
3] Create a shortcut in form of a LNK file that leads to the folder TEST-2 and place this LNK in folder TEST-3
4] Move folder TEST-2 from folder TEST-1 to folder TEST-4
5] Re-enter folder TEST-3 and follow the link to folder TEST-2
What happens? A window of the Window Explorer opens up, showing the TEST-2 folder residing in TEST-4 folder - i.e. a proper behavior occurs but in the wrong software
Why does FreeCommander cedes the task of opening the folder to a third party software? Apparently it is able to find the moved folder [by somehow coping up with a broken link] but is reluctant to open it? Where is the logic in that?
FC uses Windows Explorer to explore broken folder shortcuts
FC uses Windows Explorer to explore broken folder shortcuts
Last edited by Forez on 31.12.2022, 21:08, edited 3 times in total.
Re: FC uses Windows Explorer to explore broken folder shortcuts
This bug is still present in version 861 32-bit Public
Re: FC uses Windows Explorer to explore broken folder shortcuts
Version 880 32-bit public also suffers from it
[I corrected my initial post, as it had a profound error explaining the steps]
[I corrected my initial post, as it had a profound error explaining the steps]
Who is online
Users browsing this forum: No registered users and 132 guests