Wanted: Sample scripts to cannibalize

@Try3 Updated version is now available using the same link. The built-in help has been updated to reflect the changes. Here is an example with a dialog title:

Code:

FileDialog.exe Open C:\Users "*.ini|*.ini" "Select an INI file" false

If the dialog title is is the same as one of the special folders names (e.g. "Documents"), prefix it with a tilde (this should be a very rare situation):

Code:

FileDialog.exe Open "*.doc|*.doc" ~Documents Documents false

I haven't had time yet to look at retrieving the value from the console, but that's on my To Do.

LesFerch said:

Please see: Capture c# console application string in command variable

Yes, that's how I do it, that's how I always do it.
But the particular command used in this case thwarts me.

I'll just carry on getting the results from the Registry instead.

Denis

LesFerch said:

If the dialog title is is the same as one of the special folders names (e.g. "Documents"), prefix it with a tilde (this should be a very rare situation):

Code:

FileDialog.exe Open C:\Users "*.doc|*.doc" ~Documents Documents false

One parameter too many?

That comma in the Registry entry is making processing difficult.No, it's not.

I've been testing the new version and all seems well. I'll refine the 'calling' batch files and post back.

All the best,
Denis

Les, pokee,

I've written a pair of batch files containing the code that I will copy to individual operational batch scripts that need Folder or File dialogs.
- These batch file 'callers' are complete procedures so they can be run as demonstrators without any changes being necessary.
- I have stuck in REM lines to show where the scripts would be tailored to the needs of individual operational batch scripts. No other changes should ever be necessary.
- I have tested them in Windows 10 & Windows 11
- Both can cope with paths and filenames containing spaces and ampersands [&] and both can cope with the folder/file dialog being cancelled.
- I have written separate Dialog-SelectFolder.bat and Dialog-SelectFile.bat files because the ifs, buts and maybes in a single combined file would be to awkward to work with [I think I'd make mistakes copying the code into operational scripts].

I've zipped them up along with the current version of FileDialog.exe [which is common to both batch scripts].
FileDialog with batch file callers.zip

Using Dialog-SelectFolder.bat



Using Dialog-SelectFile.bat




If I had a day to spare, I'd also write equivalent PS1 callers to use within operational PS scripts.

Les - I did not use HKCU\Software\FileDialog ItemListM.

All the best,
Denis

pokee,

I appreciate that you're well down the road of implementing an HTA solution.
If you decide to use FileDialog.exe instead, I can explain how to 'spawn' onscreen message boxes to display your instructions to your users.
They are actually vbs MsgBoxes initiated by batch code.

You'd no doubt want to discuss things further but here is an example of such a batch file MsgBoxSpawner.
MsgBoxSpawner - PokeeVersion.zip
- It is an innocuous demonstrator.
- It is my 'template' version that I use to copy code into real batch files.
- It opens a particular variant of message box using the values set in the batch file [which are what I'd expect you to want to tailor to your own requirements].
- If the display is blank when the MsgBox opens, the display is woken up so it can be seen. This is normally only useful at the end of long procedures such as backups.
- When you close the MsgBox, the batch file tells you which button was pressed.




Best of luck,
Denis