There is this small inconvenience that I have just noticed when writing this post https://freecommander.com/forum/viewtop ... 769#p31769; at least on Windows 10 and Build 770 32-bit public
When you have for example a BAT file and create for whatever reason a shortcut to it, then that second file gets a LNK extension. And now if you right click it and go to Properties > Shortcut you will see that the >>Target<< shows the path to the original file. That is normal
But now if you try to make an icon shortcut within FreeCommander to that LNK shortcut by using the >>Customize Favorite toolbars<< option, you have to put some data in the >>Program or folder<< box, right? So you click the >>...<< icon, select >>Seek program...<<, navigate to proper folder, switch to >>All files (*.*)<< and select the LNK file. So what happens? Instead of seeing in the >>Program or folder<< box a path ending with the LNK you get to see the BAT at its end. And that beats the purpose of creating [for whatever reason] the LNK file
To workaround that issue the user has now to either manually change the end of the path; or copy it in its entirety by using the "Copy as path" entry available in the shell menu- to access which the user would have to first close the >Define favorite toolbars>> window. And al of that:
- requires some knowledge about operating system
- is inconvenient
- takes extra time and clicks
- makes FreeCommander look unprofessional
It is not a bug, as FC apparently simply chooses to read the path of the target and not the path of the LNK file itself- but that is the core of that issue
So I make a notion of switching FreeCommander to taking notice of the actual file's path and no of its target
Shortcut files should be added as LNK files and not as source files [RESOLVED]
Shortcut files should be added as LNK files and not as source files [RESOLVED]
Last edited by Forez on 15.05.2023, 14:30, edited 1 time in total.
Re: Shortcut files should be added as LNK files and not as source files
This is issue is still present in version 887 64-bit Donor Portable
And apparently limits functionality of other programs; like Everything 1.5.0.1341a x64 Portable: https://www.voidtools.com/forum/viewtopic.php?p=55933
And apparently limits functionality of other programs; like Everything 1.5.0.1341a x64 Portable: https://www.voidtools.com/forum/viewtopic.php?p=55933
Re: Shortcut files should be added as LNK files and not as source files
As far as I know, this is normal Windows behavior.
Try to open lnk file in some text editor - if the default Windows dialog for file selection is used, the target file will be opened.
Try to open lnk file in some text editor - if the default Windows dialog for file selection is used, the target file will be opened.
Re: Shortcut files should be added as LNK files and not as source files
If I am not mistaken, this is not true - to which atest this testimony: https://www.voidtools.com/forum/viewtopic.php?p=55933
Try - to see if it works?
Or try - as in "try to change your modus operandi / workflow"?
Re: Shortcut files should be added as LNK files and not as source files
https://freecommander.com/forum/viewtop ... &start=330:
So thank you Marek
This issue has been deal with now [and the problem in Everything is also no more]- Changed: Favorite tool definition - if an LNK file is selected, then the path of the file and not the target path is used
So thank you Marek
Who is online
Users browsing this forum: Ahrefs [Bot] and 57 guests