CALL/@wlf example...

Chad McWilliams chad at computiprint.com
Thu Apr 28 09:53:32 PDT 2005



> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at bestweb.net] 
> Sent: Thursday, April 28, 2005 11:47 AM
> To: 'filePro mailing list'
> Cc: Chad McWilliams
> Subject: Re: CALL/@wlf example...
> 
> 
> Quoting Kenneth Brody (Thu, 28 Apr 2005 12:22:29 -0400):
> 
> > Quoting Chad McWilliams (Thu, 28 Apr 2005 10:47:58 -0500):
> >
> > [... CALLed table ...]
> > > ::screen "T",aa:
> > > @wlfaa::msgbox "Leaving aa":
> > > @wlfab::msgbox "leaving ab":
> > > ------------------------------------------------
> > >
> > > After hitting enter, I am switched to screen T and put in 
> the field
> > aa.
> > > But moving from field to field does not generate any of 
> the message 
> > > boxes, indicating that @wlf processing is not running.
> > >
> > > Should I be able to do this?
> >
> > Events are taken from the _input_ table, just as documented.
> 
> Actually, I spoke too soon...
> 
> During input processing, events are taken from the _current_ 
> table, so they will be run in the CALLed table, assuming that 
> you are still _in_ the CALLed table.
> 
> SCREEN ends the CALL, so you are no longer in the called 
> table while the screen is being updated.
> 
> On the other hand, "POPUP UPDATE -" remains in the called 
> table, and events will be taken from there.
> 
> --
> KenBrody at BestWeb dot net        spamtrap: 

OK, that clears a lot up.  I see that mentioned in the documentation now,
but had you not pointed it out the way you did (more clearly to me anyway) I
probably would have never picked up on that reading the docs.

Thanks to all!

-Chad



More information about the Filepro-list mailing list