AndrewMozley
Programmer
I am finding that occasionally keystrokes entered into a GET field are not being immediately echoed on the screen.
This appears to happen when I have only a couple of fields defined. I enter characters into field 1, tab to field 2 and enter characters there.
If I then tab backwards to the first field, I am finding that the first two characters I enter at the beginning of that field are not being immediately echoed. They are echoed either when I enter a 3rd character into field 1, whereupon the miraculously appear, or when I tab into field 2 and enter a character there, and once again the character entered in field 1 appears. This is my program :
I have looked at the code in GETSYS.PRG, and there is a function, GetApplyKey() which within it appears to do the business of making the character appear on the screen, by calling Get:Insert() or Get:Overstrike().
If I put in an extra SAY instruction (perhaps @24,79 SAY " ") that seems to fix the problem - it seems to galvanise the GET into doing the business.
Has anyone else experienced this problem or is it a self-inflicted injury!
Thanks. Andrew
This appears to happen when I have only a couple of fields defined. I enter characters into field 1, tab to field 2 and enter characters there.
If I then tab backwards to the first field, I am finding that the first two characters I enter at the beginning of that field are not being immediately echoed. They are echoed either when I enter a 3rd character into field 1, whereupon the miraculously appear, or when I tab into field 2 and enter a character there, and once again the character entered in field 1 appears. This is my program :
Code:
#include "inkey.ch"
#include "setcurs.ch"
FUNCTION MAIN
LOCAL lRow := 0, lName1, lName2
PRIVATE GetList:= {}
SET SCORE OFF
SET COLOR TO B/W, + GR/B
@ 0, 0 CLEAR TO 24, 79
* Test the basic GET system
lName1 := SPACE(8)
lName2 := SPACE(8)
@ 1,1 SAY "Name 1" GET lName1
@ 2,1 SAY "Name 3" GET lName2
READ
RETURN .T.
I have looked at the code in GETSYS.PRG, and there is a function, GetApplyKey() which within it appears to do the business of making the character appear on the screen, by calling Get:Insert() or Get:Overstrike().
If I put in an extra SAY instruction (perhaps @24,79 SAY " ") that seems to fix the problem - it seems to galvanise the GET into doing the business.
Has anyone else experienced this problem or is it a self-inflicted injury!
Thanks. Andrew