FileSelectFile & Shortcuts & Windows 10

Report problems with documented functionality
User avatar
lmstearn
Posts: 211
Joined: 11 Aug 2016, 02:32
GitHub: lmstearn
Contact:

FileSelectFile & Shortcuts & Windows 10

03 Mar 2019, 07:32

Hi there,
Not a bug report, but more of an observation on the way the Shell handles the file dialogs in the latest editions of Windows:
Create a shortcut to Notepad: as per attached:
Notepad_Lnk.7z
(760 Bytes) Downloaded 17 times

Code: Select all

FileSelectFile, OutputVar, 3,, Open a file`, Shortcuts resolved, (*.exe; *.bat; *.com; *.cmd; *.pif; *.msc; *.lnk; *.scr)
Open the dialog and select the lnk file, and there is no more navigation into the folder via the folder shortcut.

Worth noting, that in removing *.lnk from the filter, the link still shows in the dialog for :

Code: Select all

FileSelectFile, OutputVar, nOptions,, Open a file`, Shortcuts resolved, (*.exe; *.bat; *.com; *.cmd; *.pif; *.msc; *.scr)
... regardless of what is in nOptions or whether the *.exe filter is present or not.
It used to work, but unable to recollect from what epoch. :P
No big deal, as what V2 is offering will be an improvement.
Thanks for reading!
Edit: The CLSIDS (e.g. Start Menu Folder, My Computer) don't seem to work either in FileSelectFile as they do in the Run command.
Built-ins like A_StartMenu and A_ProgramsCommon still work with FileSelectFile.
The online documentation is marking a change in parameters for the next release:
FileSelectFolder, OutputVar , StartingFolder, Options, Prompt
:)
:arrow: itros "ylbbub eht tuO kaerB" a ni kcuts m'I pleH

Return to “Bug Reports”

Who is online

Users browsing this forum: No registered users and 4 guests