forums.silverfrost.com

[PaulLaidler]

A new format code %cd (Common Dialog) has been added to the latest release.
This provides an alternative to calling routines such as get_filtered_file@.
The following sample code illustrates how it works.

[PaulLaidler]

Here is an short introduction to %cd.

New new format code %cd has be added that generates the standard Microsoft Open/Save As file dialog. This is an alternative to calling get_filtered_file@ or get_multiple_filenames@ and provides greater choice as well as a platform for further development.
Here are the options:
integer,parameter:: MAXFILES = 10
integer(7) hwnd
integer flags
character(80) fileName(MAXFILES) !For multi-selection
character(80) shortFileName,initialDir
character(256) dir
iw = winio@("%cd[hwndowner]&",hwnd)
iw = winio@("%cd[title='Open Fortran files']&")
iw = winio@("%cd[file]&",filename)
iw = winio@("%cd[initialdir]&",initialDir)
iw = winio@("%cd[flags]&",flags)
iw = winio@("%cd[saving]&")
iw = winio@("%cd[filter='All files (*.*)']&")
iw = winio@("%cd[maxfiles]&", MAXFILES)
iw = winio@("%cd[showreadonly]&")
iw = winio@("%cd[shortfile]&",shortFileName)
iw = winio@("%cd[rootdir]&",dir)

[hwndOwner] is the parent HWND obtained from %hw.
[title] is the caption for the dialog.
[fileName] is for the selected file.
[initialDir] varies with the operating system but usually provides the initial folder when the dialog is first used.
[flags] is the value used in the Microsoft OPENFILENAME structure. ClearWin+ provides a default value that is accessed via the value returned by winio@ during construction. Other bit flags can then be added and set using this option.
[saving] provides for a "Save As" dialog as opposed to a "File open" dialog.
[filter] can be used more than once and provides a list of file filters. An alternative form uses a pipe symbol '|' as in
iw = winio@('%cd[filter="Fortran files|*.f95;*.for"]&')
[maxfiles] is the largest number of files for a multi-selection Open dialog.
[showreadonly] causes the read only check box to be displayed.
[rootdir] is for the selected drive and folder name.
[shortfile] is for the selected file or files without the path.

[wahorger]

Paul,

I'm looking forward to using this!

A question: Is "browse_for_folder@" and/or "browse_for_folder1@" extension using this process a possibility or in the plan? My code still crashes when the user selects a "New Folder" using "browse_for_folder1@".

Thanks for creating a new way that is extensible!

Bill

[PaulLaidler]

Bill

Yes. There are other standard dialogs, like "browse for folder" that are planned using this approach.

[wahorger]

Does the ClearWin info request

[PaulLaidler]

No, but I will aim to take a look and provide something similar.

[wahorger]

Thanks, Paul.

[PaulLaidler]

I have added [filter_item_selected] which corresponds to an integer used for both input and output....

integer filter_item_selected
filter_item_selected = 0
iw = winio@("%cd[filter_item_selected]&",filter_item_selected)

This index starts at 1. A zero value can be used on input for the default.

CLEARWIN_INFO@('FILTER_ITEM_SELECTED') will also still be available for output.

[wahorger]

Thanks so very much, Paul!

Bill

[wahorger]

Paul,

When will [filter_item_selected] be available in a DLL for download?

A couple of observations based on some experimenting today.

[rootdir] and [initialdir] seem to have the same purpose, but this is unclear. Could you elaborate on this?

If [rootdir] is not used and [initialdir] is used, it appears to work just fine.

If I use the same variable to set [rootdir] and [initialdir], I cannot consistently traverse the folder paths up/down. Sometimes it works, sometimes it doesn't. If they are different variables, then I've always been able to traverse.

When specifying filters, if you use the pipe syntax ("|"), then you get the title (name) of the filter but not the specifics on what it is filtering. I can see how this syntax could be helpful! Thanks for having both methods!

I have tried [saving] and it nicely changes the filter title, indicating the user can change the type. However, when I type in a new name without the extent, the name returned does not have the extent appended to it [(just like get_filtered_file@()], so knowing which extent is selected gets more importance [to then use set_suffix1@()].

What I really like about [saving] is that if I select an existing file, it will tell me and allow me to either back out, retry, or cancel. I can use that to remove a lot of additional checking code for over-writing existing files. Awesome.

Still more experimenting to do. If I can come up with a small example of the inconsistent behavior to make it consistent, I'll post it.

[PaulLaidler]

Bill

[filter_item_selected] will already be available for 64 bits via the latest DLL. Please see the link added to the sticky post dated August 1.

For 32 bits the situation is a little more tricky and, if you need it, I could provide you with a separate download for the latest salflibc.dll.

%cd and routines like get_filtered_file@ make calls to the Microsoft functions GetOpenFileName and GetOpenFileName. These use the OPENFILENAME structure that is described here https://learn.microsoft.com/en-us/windows/win32/api/commdlg/ns-commdlg-openfilenamea.

This link provides details of the expected behaviour for initialdir etc. and indicates that in some respects the behaviour of these functions varies from one operating system to another.

In particular I have noted that, for me, initialdir only works for the first call to these functions within the current instance of the application. It seems to me that there may be no standard outcome.

[wahorger]

Paul, thanks for the explanation of GetOpenFileName and GetOpenFileName. I will look at these descriptions and check out the link to gain a better understanding. I still have "playing" to do!

I would appreciate access to the 32-bit salflibc.dll with this capability. Thank you for offering.

Bill

[PaulLaidler]

Bill

I have sent you a personal message.

[wahorger]

Paul, thanks for the file. I have a few more questions.

In your message of 06 July, in your short introduction, you indicate [flags] as an option, with the explanation that the value of the current flag is returned during construction so that one can add/delete flags as required. I'm unsure how to do that.

if I include the construct

[PaulLaidler]

Bill

I think that it is very unlikely that [flags] will be useful.

In the example above, at any point you can examine the iw return value. It will give you the flags value at the current point in the construction.

You can then bitwise "add to" or "subtract from" this value and use the modified result with %cd[flags].

You would probably want to do this as the last %cd call.