QM / FlashGUI code examples for the group

[gordonf]

Hi All,

I have uploaded some code examples for the group.


These programs are based on QM 2.8.6 and FlashGUI 2.2.7.


I am an amateur at programming.
Do not waste time telling me how bad my code stinks - I already know
that.


MAIN_SKELETON
If you want to build a multi-screen application this code will
function as the main calling program for all the other screens,
F1 will let you build your own CONTEXT sensitive help screens that
can be edited and added to at any time.
ALT-F12 will print a graphical picture of your FlashGUI window while
the window is running.

SUBROUTINE_SKELETON
This code is the base for ALL subroutine windows called by the
Main Skeleton code(above).

GF_ADD_SCREEN
GF_REMOVE_SCREEN
These 2 routines help keep the executing code in sych with the
open FlashGUI windows. The code is written so that when a screen
(window) is deleted then ALL child screens are closed and all the open
code is terminated. These routines are called by MAIN & SUBROUTINE in
all applications. They are candidates for GLOBAL Cataloging.

HELP_ROUTINE
This routine creates the context sensitive help screens mentioned
in Main Skeleton (above). BE VERY CAREFUL - this routine will create a
file.

DICT_BUILDER
This is a Dictionary item editor that I made for FlashGUI. I
really like it 'cause it helps me build dictionaries a lot faster.
Your mileage may vary. After the 1st item is added to the dictionary
all additional items will have DEFAULT prompt data. Helps when making
items that are a lot alike. Select an item(double-click) from the LIST
feature and it will be brought back for edit. For I-type dict items
you can use a multi-line input screen by pressing F4 at the expression
input line.


I have lightly used all of the above.
Severely beating on the code will probably find bugs.

All of these code examples were written by me and are FREE for any of
you to use in any way that you see fit.

( Printing them out and lining the cat box is one way that they could
be used.)

Here comes the catch:
I would like to learn better ways of coding and improving the above
work. PLEASE if you use any of this code then post any changes or
improvements to this forum.

For those of you who want to brag about how much better you are at
coding I can be reached at gor...@bellsouth.net.


Gordon French
Gordon French Accounting, Inc
Fort Lauderdale, Florida

[GVP]

Gordon,

MANY THANKS for your examples.

I know, that you have the nice tool of Month/calendar. It can be
interesting too.

Regards,
Grigory

[gordonf]

Grigory,

Thanks for the reminder about CALENDAR.

I have posted 2 versions of calendar.
My original one, calendar_gordon and a modified version from Alexei,
calendatr_alexei_2.
The main difference is some interesting code in the timing loop that
happens when one of the buttons is held down.

Gordon French

[GVP]

Gordon,

Your code is more shorter than expected. Very clear. I like good
formated code with clear logic.
Calendar code is very compact.

Regards,
Grigory