Re: field values

Path: emory!sol.ctr.columbia.edu!spool.mu.edu!sdd.hp.com!hplabs!nsc!pyramid!infmx!news From: cortesi@informix.com (David Cortesi) Newsgroups: comp.databases.informix Message-ID: <1992Feb21.172636.17739@informix.com> Date: 21 Feb 92 17:26:36 GMT References: <paulb.698573226@p4.cs.man.ac.uk> Sender: news@informix.com (Usenet News) Reply-To: cortesi@informix.com Organization: Informix Software, Inc. In article <paulb.698573226@p4.cs.man.ac.uk> paulb@p4.cs.man.ac.uk (Paul Bean) writes: > Firstly thanks to everyone who mailed/posted help with regard to > before/next field question. The fgl_lastkey and fgl_keyval functions > were particularly useful - Are these documented anywhere, we do not > appear to have them in any of the stuff we have ? The following functions are documented in the "4.1 Supplement" manual for Informix-4GL: fgl_getenv() -- gets environment variables fgl_keyval() -- returns binary code of logical key like "left" fgl_lastkey() -- returns binary code of last key pressed field_touched() -- TRUE if user has modified specified field(s) get_fldbuf() -- returns contents of specified field(s) The same manual documents other major improvements to the user interface statements such as before/after input, before/after construct, before/after field and on-key support for construct, etc etc. > ...is there a way to find out what the contents of a field are before you > have left it. I would like to give a popup list of values whilst > still in the field and use the string typed in so far. that's the purpose of get_fldbuf(). There used to be a secret undocumented method you could work out by reverse-engineering the generated .ec code, but this is supported & documented.