Ben, Marc

This is the same idea I had, but I am still investigating.
I found in Anne Gillian's book INSIDE RBASE on page 2-23 a
thing about playback files executing on the next keystroke
If an ENTRY eep like this: inacol.eep

SET VAR vm_frm TEXT = NULL
SET VAR vm_col TEXT = NULL
SET VAR vm_cvalword TEXT = 'FORM_NAME'
SET VAR vm_frm = (CVAL(.vm_cvalword))
SET VAR vm_cvalword TEXT = 'FORM_FIELD_NAME'
SET VAR vm_col = (CVAL(.vm_cvalword))
CLEAR VAR vm_cvalword
RETURN

Before the form loads run this:

SET VAR vcommand = ('SET KEYMAP [ALT]H=' & CHAR(39) +  'RUN' + +
' hlpsys.rmd' + CHAR(39))
&vcommand

Then in a playback test for the ALT H

IF it is and ALT H then fire the hlpsys.rmd >>>

IF vm_frm IS NOT NULL AND vm_col IS NOT NULL THEN
  SET VAR vm_hlpmsg TEXT = NULL
  SELECT hlpmsg INTO vm_hlpmsg INDICATOR vm_i FROM syshlp WHERE hlpform
= .vm_frm AND hlpcol = .vm_col
  EDIT USING syshelp AT 1,1,50,200 noheader
ENDIF



Haven't worked out all the bugs, but moving at a snails pace

Jim Limburg



Ben Petersen wrote:
> 
> Marc,
> 
> CVAL can identify the form and field. You could have a table with a
> column to ID form&field with the appropriate help text in another
> column and another form to display the text... the trick is activating
> the eep that displays the form.
> 
> I thought getkey might be put at the front of each entry eep, but
> couldn't come up with a way to pass through the captured
> keystroke if not the "help" key.  It would be nice to avoid learning
> another tool, but that may be the most direct solution.
> 
> Ben Petersen
> 
> On 4 Sep 2001, at 13:44, marc wrote:
> 
> > Hi all
> >
> > I was dreaming about an easy way to make a help
> > system and manual for users.
> >
> > Form help screens,  While designing a form have a Form Title box
> > and have about 4-8k of help notes, pressing F1 while using the form
> > will display the help screen.
> >
> > Field help messages, Have a Form Title box to link to the form
> > and a Field name box, 1-2k of help notes, press Shift F1 to display
> > the help message. Of course still have the small message for each
> > field at the bottom of the form.
> >
> > Be able to print this out in a printed manual with the field notes
> > after the form notes and create a Windows help file.
> >
> > This way when we make an app we can document what each field and
> > form one time and create help files and printed manuals.
> >
> > Just thinking
> > marc
> >
> >
> >
> >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >

Reply via email to