display help file

[Richard Kreiss]

> -----Original Message-----
> From: Jose Lerebours [mailto:fpgroups at gmail.com]
> Sent: Monday, January 10, 2011 1:46 PM
> To: rkreiss at gccconsulting.net
> Cc: filePro
> Subject: Re: display help file
> 
> On Mon, Jan 10, 2011 at 1:14 PM, Richard Kreiss
<rkreiss at gccconsulting.net>
> wrote:
> > I have a help file which displays properly on a Windows system by
> > pressing F1.
> >
> > Is there a way to have the help file displayed using the M key?
> >
> > I can copy everything in the help file and use the heading keyM and then
> do:
> >
> > @keyM:
> >        Then: Help("keyM");END
> >
> > Just wondering if there is an easier way of doing this.
> >
> 
> on a totally unrelated matter, I remember developing a custom help system
> where pressing F10 while in update mode a help window traveled with the
> cursor from field to field.  F10 turned help ON/OFF; if ON, the window
> popped up, otherwise if not.
> 
> The concept was very simple.  I simply used a filePro file with a couple
of
> fields.  The fields were
>  - file name: Name of file to which help entry was associated
>  - field name: Name of field to which help entry was associated
>  - screen name: Name of screen to which help entry was associated
>  - X coord: X coordinate where to place the help window
>  - Y coord: Y coordinate where to place the help window
>  - pop-up screen name: Name of screen to display as help screen
> 
> I normally defined the help screens within the active file itself.  I used
_h as a
> prefix to the help screen so that I can easily identify them as help
screen.
> Normally, _h0155
> meant help screen for screen 1 field 55.
> 
> The code was very simple.  Look up a record matching built key, if found,
pop
> up the screen accordingly ... This always gave me a WOW! from my users
> since they found that it was not intrusive and allowed them to type while
> assistance was offered.  I liked it since it kept phone calls to a minimum
...
> very often suggesting "Press F10 for an answer ..." was all I needed to
do.
> 
> Regards,


Interesting but as you said, unrelated.

The help being shown are the available single keys made available using the
@key function.  

Yes, I can create rolling prompts at the bottom of the screen as I have done
for a number of files in the application.  

However, for my own sanity, I put all of the possible single key strokes and
their function into the help file.  This allows me one place to quickly see
if a key is already being used for another function.

In fact, with the addition of DOKEY, there are a few keys which are doing
double duty.

In a few cases, in this application, I have made @keyM into a menu function
where the user can select the @key function to run.  This is easier the
scrolling through prompt changes at the bottom of the screen.  I was also
able to add HELP to the menu using the original help file copied to a new
header and then adding a more detailed explanation of each function using
F9.

Richard