Re: ON KEY in CONSTRUCT

In article <9309170140.AA29939@godzilla.informix.com>, Jonathan Leffler (johnl@informix.com) writes: :> :> >From: alex@lucas.MREC.AR (Maria Alejandra Perez Weiss) :> >Subject: ON KEY in CONSTRUCT . . . (stuff deleted) :> >I've just found a weird behaviour of the CONSTRUCT statement. :> > :> >I tried to use ON KEY in order to call a help function and modify :> >the input buffer with DISPLAY. :> >(That's exactly what the manual suggests to do) :> >But ... :> >a) if the called function has an INPUT statement, the :> > DISPLAY shows the new value and it is inmediately cleared! :> > (and the buffer is empty again) . . . (stuff deleted) :> >d) everything works ok if I compile it with c4gl instead of :> > generating p-code with fglpc :> > Maria includes some sample code in her mailing, that shows the ON KEY clause in the construct statement calling up a NEW FORM for an INPUT ROUTINE, getting a value, closing the NEW form, returning a value, and then displaying the value on the OLD form that is active for the construct statement. :> I guess I should answer this. However, as usual, I must point out that :> these comments have no official standing. :> ... (stuff deleted) :> 3. COMMENTARY :> * I believe that the comment is saying that if you need to use the :> same form fields twice, you should: :> Either :> - Open a new window with the same form file :> Or :> - Open the same form file with a new form name ... :> * There are bugs in this area. In general, opening a new window is :> the safest approach. :> :> 4. POSSIBLE INTERPRETATION :> * Recursive input is not at the moment supportable. In general, you :> will find it fails. ... :> :> Yours, :> Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> :> It appears Jonathan's comments don't actually apply to Maria's problem, as she IS using a different form. I am getting the same bug that Maria has. I am using Version 4.10.UE2 for both the c4gl and pcode on a sun sparc. The screen buffer is not taking the data from the display statement in the pcode version if there was an input statement invoked during the on-key processing, but it does work fine with the compiled version. Is this a known bug? -- Colin McGrath Internet: colin@scdipc0.ueci.com Raytheon Engineers & Constructors Inc. Voice: 215-422-3449 30 S. 17th St FAX: 215-422-3363 Philadelphia, PA, 19101 #include <disclaimer.h>