Using Intel® Visual Fortran to Create and Build Windows*-Based Applications

Download PDF
ID 757211
Date 7/23/2021
Public
Document Table of Contents
Document Table of Contents x
Using Intel® Visual Fortran Compiler to Create and Build Windows*-Based Applications
Using Intel® Visual Fortran Compiler to Create and Build Windows*-Based Applications x
Legal Information Introduction Creating Windowing Applications Creating and Using DLLs Using QuickWin Using Dialog Boxes for Application Controls
Introduction x
Notational Conventions Related Information
Creating Windowing Applications x
Understanding Coding Requirements for Fortran Windowing Applications Using Menus and Dialogs in SDI and MDI Fortran Windowing Applications Sample Fortran Windows Applications Advanced Graphics Using OpenGL
Creating and Using DLLs x
Coding Requirements for Sharing Procedures in DLLs Coding Requirements for Sharing Data in DLLs Building Dynamic-Link Libraries Building Executables that Use DLLs
Using QuickWin x
Special Naming Convention for Certain QuickWin and Windows* Graphics Routines Comparing QuickWin with Windows*-Based Applications Using Windows API Routines with QuickWin Types of QuickWin Programs The QuickWin User Interface USE Statement Needed for Fortran QuickWin Applications Creating QuickWin Windows Using QuickWin Graphics Library Routines
Types of QuickWin Programs x
Fortran Standard Graphics Applications Fortran QuickWin Graphics Applications
The QuickWin User Interface x
Default QuickWin Menus
Creating QuickWin Windows x
Accessing Window Properties Creating Child Windows Giving a Window Focus and Setting the Active Window Keeping Child Windows Open Controlling Size and Position of Windows
Using QuickWin Graphics Library Routines x
Selecting Display Options Checking the Current Graphics Mode Setting the Graphics Mode Setting Figure Properties Understanding Coordinate Systems Adding Color Writing a Graphics Program Displaying Graphics Output Storing and Retrieving Images Customizing QuickWin Applications QuickWin Programming Precautions Simulating Nonblocking I/O
Understanding Coordinate Systems x
Text Coordinates Graphics Coordinates Setting Graphics Coordinates Real Coordinates Sample Program
Adding Color x
Color Mixing VGA Color Palette Using Text Colors
Writing a Graphics Program x
Activating a Graphics Mode Drawing Lines on the Screen Drawing a Sine Curve Adding Shapes
Displaying Graphics Output x
Drawing Graphics Displaying Character-Based Text Displaying Font-Based Characters Using Fonts from the Graphics Library
Using Fonts from the Graphics Library x
Available Typefaces Initializing Fonts Setting the Font and Displaying Text SHOWFONT.F90 Example
Storing and Retrieving Images x
Transferring Images in Memory Loading and Saving Images to Files Editing Text and Graphics from the QuickWin Edit Menu
Customizing QuickWin Applications x
Enhancing QuickWin Applications Controlling Menus Changing Status Bar and State Messages Displaying Message Boxes Defining an About Box Using Custom Icons Using a Mouse
QuickWin Programming Precautions x
Using Blocking Procedures Using Callback Routines
Using Dialog Boxes for Application Controls x
Using the Resource Editor to Design a Dialog Box Writing a Dialog Application Summary of Dialog Routines Understanding Dialog Controls Using Dialog Controls Using ActiveX* Controls
Using the Resource Editor to Design a Dialog Box x
Setting Control Properties Including Resources Using Multiple Resource Files The Include (.FD and .H) Files
Writing a Dialog Application x
Initializing and Activating the Dialog Box Using Dialog Callback Routines Using a Modeless Dialog Box Using Fortran AppWizards to Help Add Modal Dialog Box Coding Using Fortran AppWizards to Help Add Modeless Dialog Box Coding Using Dialog Controls in a DLL
Understanding Dialog Controls x
Using Control Indexes Available Indexes for Each Dialog Control Specifying Control Indexes
Using Dialog Controls x
Using Static Text Using Edit Boxes Using Group Boxes Using Check Boxes and Radio Buttons Using Buttons Using List Boxes and Combo Boxes Using Scroll Bars Using Pictures Using Progress Bars Using Spin Controls Using Sliders Using Tab Controls Setting Return Values and Exiting
Using ActiveX* Controls x
Using the Resource Editor to Insert an ActiveX Control Using the Intel® Fortran Module Wizard to Generate a Module Adding Code to Your Application Registering an ActiveX Control
Using Intel® Visual Fortran Compiler to Create and Build Windows*-Based Applications

Giving a Window Focus and Setting the Active Window

When a window is made active, it receives graphics output (from ARC, LINETO, and OUTGTEXT, for example) but is not brought to the foreground and thus does not have the focus. When a window acquires focus, either by a mouse click, I/O to it, or by a FOCUSQQ call, it also becomes the active window. When a window gains focus, the window that previously had focus will lose focus.

If a window needs to be brought to the foreground, it must be given focus. The window that has the focus is always on top, and all other windows have their title bars grayed out. A window can have the focus and yet not be active and not have graphics output directed to it. Graphical output is independent of focus.

Under most circumstances, focus and active should apply to the same window. This is the default behavior of QuickWin and a programmer must consciously override this default.

Certain QuickWin routines (such as GETCHARQQ, PASSDIRKEYSQQ, and SETWINDOWCONFIG) that do not take a unit number as an input argument usually affect the active window whether or not it is in focus.

If another window is made active but is not in focus, these routines affect the window active at the time of the routine call. This may appear unusual to the user since a GETCHARQQ under these circumstances will expect input from a grayed, background window. The user would then have to click on that window before input could be typed to it.

To use these routines (that effect the active window), either do I/O to the unit number of the window you wish to put in focus (and also make active), or call FOCUSQQ (with a unit number specified). If only one window is open, then that window is the one affected. If several windows are opened, then the last one opened is the one affected since that window will get focus and active as a side effect of being opened.

The OPEN (IOFOCUS) parameter also can determine whether a window receives the focus when a I/O statement is executed on that unit. For example: 

  OPEN (UNIT = 10, FILE = 'USER', IOFOCUS = .TRUE.)

With an explicit OPEN with FILE='USER', IOFOCUS defaults to .TRUE. For child windows opened implicitly (no OPEN statement before the READ, WRITE, or PRINT) as unit 0, 5, or 6, IOFOCUS defaults to .FALSE..

If IOFOCUS=.TRUE., the child window receives focus prior to each READ, WRITE, or PRINT. Calls to OUTTEXT or graphics functions (for example, OUTGTEXT, LINETO, and ELLIPSE) do not cause the focus to shift. If you use IOFOCUS with any unit other than a QuickWin child window, a run-time error occurs.

The focus shifts to a window when it is given the focus with FOCUSQQ, when it is selected by a mouse click, or when an I/O operation other than a graphics operation is performed on it, unless the window was opened with IOFOCUS=.FALSE.. INQFOCUSQQ determines which unit has the focus. For example: 

    USE IFQWIN
   INTEGER status, focusunit
   OPEN(UNIT = 10, FILE = 'USER', TITLE = 'Child Window 1')
   OPEN(UNIT = 11, FILE = 'USER', TITLE = 'Child Window 2')
 ! Give focus to Child Window 2 by writing to it:
   WRITE (11, *) 'Giving focus to Child 2.'
 ! Give focus to Child Window 1 with the FOCUSQQ function:
   status = FOCUSQQ(10)
    ...
 ! Find out the unit number of the child window that currently has focus:
   status = INQFOCUSQQ(focusunit)

SETACTIVEQQ makes a child window active without bringing it to the foreground. GETACTIVEQQ returns the unit number of the currently active child window. GETHWNDQQ converts the unit number into a Windows handle for functions that require it.

Parent topic: Creating QuickWin Windows
Level Two Title