another newbie question

It's explained in the in-program 'help' file.  I don't have in front of me as I type this on an iPad but, as far as I can recall, as long as you have added APPGRAPHICS using the SF Package Manager, you just put, USE APPGRAPHICS near the start of every program which uses this library then put in as many sub program CALLs to the library as you like.

In case this doesn't work, you may need to provide some settings in the SF project options.  To find out what, if anything is needed, use the SF startup page to open one of the relevant examples, and look in the project options for the example you have selected.

If the above is all cobblers then I'm sure one of the other regulars to this forum will chip in with correct advice.

I hope you get it working because Jeff's APPGRAPHICS is a fabulous extension to SF, which, at a single extraordinary stroke, catapults SF from nowhere, fully into advanced Fortran-for-Windows programming.

By the way, the SIGSEGV problem I had when using the debugger to examine code containing a call to th DISLIN library to display a file selection dialog box, remains a problem when using a cal to AppGraphics to do the same thing.  On present evidence, it seems most likely that there's a bug in the 'DBG' debugger, not in SF, which is causing this.  It does not impede use of the file selection dialog in programs.  It just crashes the debugger.
---
John

Don,

If you want to use packages with Simply Fortran, you'd need to first get a SF Package Manager account.  There are a number of useful, pre-configured packages available.

However, if you're looking for the file selection dialogs, you can simply use AppGraphics, which is included with Simply Fortran as of version 2.19.  The File Dialogs are explained int the Common Dialogs section.  Basically, all you would need to do is:

program fileselect
use appgraphics
implicit none

    character(len=256)::filename
    
    filename= repeat(' ', 256)
    if(dlgopenfile(filename)) then
         Print *, "You've selected "//trim(filename)
    else
        Print *, "No file was selected"
    end if

end program fileselect

As of version 2.20, you no longer need to set any other project flags.  When Simply Fortran detects you've used AppGraphics anywhere, it adds the appropriate flags to the Makefile.

Don,

If you change a Fortran source file that contains a module, does building show that Fortran source file being recompiled?

The "modules" subdirectory contains only ".mod" files, which are products of compilation.  They are not the compiled code, though.  Rather, they represent a human-unreadable description of a module found in your Fortran source code.  When compiling Fortran source code that uses a module, the compiler will open the corresponding ".mod" file and read in the description of the module, including all public variables, types, and procedures.  Module files (the ".mod" files, not your Fortran source code) do not necessarily get recreated each time you build a source file.  They only get built if the public module description changed (like you added another public variable to a module).

I'm not sure why you're seeing the behavior you're describing.  Could you post the contents of your Makefile (from "View Makefile..." in the Project menu) and let us know which Fortran source file and module in said file that you're modifying?  I can then try to determine why the final target isn't updating when you change the source code.