General Notes

        Genindex, Help, and Popup are support programs and functions for
        the BOSSDEMO program.  They can, however, serve as valuable aids
        to you in the creation of help screens and popup menus. The code
        is provided to demonstrate how the functions in The Window BOSS
        can be used to create online help screens and popup windows.

        Both the C and assembly functions make very heavy use of
        pointers.  The code contains numerous checks to ensure that
        memory outside of that in use by the program is not corrupted.
        If you attempt to do something that would cause memory to be
        corrupted an error message will appear and your program will
        exit.  This message will usually say that a bad handle was passed
        to some function.  You can, if you wish, remove this check by
        modifying the "wns_err" function in the wn_sup.c file.

        Generally speaking, the members of the window control block
        (refer to windows.h) should not be modified unless you are
        familiar with how they are used by the various functions.

        Although the routines appear to support the multi page
        capabilities of the IBM Color Card, actual support of this
        feature has not been implemented.  Invoking the functions with
        references to video pages other than 0 might produce interesting
        but undesired results.

        If you are upgrading from a previous version of The Window BOSS
        be sure to re-compile and re-link your application.  This will
        eliminate the possibility of any "unusual" errors due to changes
        that may have been made to either the functions or the window
        control block structure.

        Several global symbols are used by the various functions:

                                 int wn_dmaflg;
                                 int wn_sbit;

             wn_dmaflg when TRUE enables direct writes into video ram.
             This is the default setting and should work in all cases.
             Setting wn_dmaflg to FALSE will disable these direct writes.
             When wn_dmaflg is FALSE the BIOS video routines are used.
             This results in slower screen updates.  However, this method
             does have the advantage of being considered "well behaved"
             by IBM's Topview, Microsoft's Windows, and DESQ.

             wn_sbit controls the window refresh rate on systems with
             color cards.  When set to SLOW (defined in windows.h) window
             displays will appear to be painted on the screen rather than
             flash displayed. This is the default value.  Setting wn_sbit
             to FAST enables flash displays. Artistic use of wn_sbit can
             give your application that extra visual touch. Experiment!

             The best way to manipulate the method by which windows are
             updated is via the wn_dmode() function.  Calling
             wn_dmode(PAINT) causes the image to be painted while
             wn_dmode(FLASH) causes the image to be flash updated. This
             is the preferred method.  Please keep in mind that windows
             are always flash updated on monochrome systems.

        From a performance standpoint, the fastest (flicker & snow free)
        screen updates will occur with wn_dmaflg=TRUE and wn_sbit=FAST.
        The key words here are flicker and snow free.  Scrolling speed
        can be increased with, a proportional increase in flicker
        (perhaps), by using wn_scroll() function to set the scrolling
        method for the window to BIOS.  This technique will provide the
        fastest screen updates and scrolling on color systems.

        Several of the compilers support a compile time command line
        parameter that results in structures being byte aligned instead
        of word aligned.  In all cases, the default (i.e. no command line
        parameter) option was used to compile the modules in the various
        libraries.

        Borland Turbo C users who prefer "The Integrated Environment"
        over the "Command-Line Version" MUST define the symbol
        "BORLAND=1". (Select Options, Compiler, Defines and enter
        "BORLAND=1"in the dialogue box without quotes and in upper case.

        Microsoft Version 5.0 libraries were generated using the the
        "/Zl" command line parameter.

        Microsoft QuickC users who prefer the programming environment
        must select EXE as output and use the DOS shell (from the FILES
        MENU) to test run their application.  Program lists must always
        be created and include MSQCPE.LIB.  We have found the programming
        environment to be very useful for editing and syntax checking but
        somewhat limited in other areas (i.e. medium model support only).
        Additionally, MSCV4=1 must be defined in the run options dialog
        box.

        Programs such as Wordstar and Lotus change the video mode when
        they run.  If your system is equipped with a color monitor and
        your windows are appearing in black and white issue a call to
        v_smode to set the video mode to 3.  Alternatively, you can use
        the "MODE CO80" command at DOS level before you run your
        application.

        PLEASE - Pass along your comments.  The Window BOSS is your tool.
        If, heaven forbid, you find any logic errors let us know.  We are
        committed to making The Window BOSS the best price performer
        available.  Call, write, or if you prefer, you can reach Phil
        Mongelluzzo via CompuServe [71565,1001].  Fido fans can leave mail
        on our support BBS at (203)-271-1579. There is no reason to sit,
        steam, or complain to those who can not provide any real form of
        support.  Lastly, if you use The Window BOSS, register your copy.
        The Shareware System will only work if you support it!