FC uses Windows Explorer to explore broken folder shortcuts
Posted: 24.06.2018, 16:48
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?
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?