CALL/@wlf example...

[Nancy Palmquist]

Chad McWilliams wrote:

> OK, here's a short example of what I'm trying to do:
> 
> ------------------------------------------------
> cust/prc.test: (run as input processing)
> 
> :::aa(1,.0);ab(1,.0);ac(2,.0):
> @wef1::msgbox "Hit Enter":
> ::call ("test2"):
> ::end:
> 
> cust/prc.test2
> ::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?
> 
> -Chad McWilliams
> 
> 
> 
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
> 
Chad,

If you have not noticed, SCREEN will end a call table if it is executed 
in the flow of the table.  If it is in @when processing, it will work as 
expected if the screen name is not given.

So be careful about how you use SCREEN.

I disagree with Ken - in my programming @wef/@wlf and such do work in 
called tables.

instead of SCREEN "T",aa use the following:

POPUP UPDATE - "T",aa

Then the following @when will work:

@wlfaa if something
	then: screen,aa

I had second thoughts after I wrote this and when back to check my 
processing and sure enough the @wlf and @wef logic is executed from the 
call.  I do not have the same @wlf labels in my INPUT table, if I did 
maybe they would be executed instead.

But that is what I have working.  It should work for you also.

Nancy

Hope that helps.  Ken I am sorry to disagree but I am sure they are 
working that way.

Nancy



-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com