a_user.key.value Does not work as I was hoping

[MikeData]

I want to open the next page or go back by using the right and left arrows keys.
On the form ONKEYEVENT.
1 The right arrow advances but sometimes advances 2 records, (I tried to slow down the repeat and rate)
There are no more tab positions beyond the sitting field.
2 The left arrow moves in the form to prior tab positions and do not move the form to previous record.
Using a button, and click works.
Is this code wrong? Any advise?

If a_user.key.value="{RIGHT}" Then
a_user.key.handled=.T.
' If a_user.key.event = "RIGHT" Then
parentform.fetch_next()
If a_user.key.value="{LEFT}" Then
a_user.key.handled=.T.
' If a_user.key.event = "LEFT" Then
parentform.fetch_Prev()
End If
End If

[MoGrace]

Re: a_user.key.value Does not work as I was hoping

You might try mapping a different key to perform the action. I use the ' * ' to do this on a form where the user is entering numeric data from the numeric keypad. Or you might try adding the Shift or Ctrl key to make it a hot key since the arrow keys already have a directional movement...

[Stan Mathews]

Re: a_user.key.value Does not work as I was hoping

Completely unclear to me why you ignored the example in the documentation.

If a_user.key.value="{RIGHT}" Then
	a_user.key.handled=.T.
	IF a_user.key.event = "down" THEN
		parentform.fetch_next()
	End if
end if
If a_user.key.value="{LEFT}" Then
	a_user.key.handled=.T.
	IF a_user.key.event = "down" THEN
		parentform.fetch_Prev()
	End If
End If

[MikeData]

Re: a_user.key.value Does not work as I was hoping

Thanks Robin. In this case I was trying to imitate like other apps or games.
There are other features, using the mouse for a while, becomes uncomfortable. Also I have to keep the mouse in a certain location.
Is minor, but I was hoping to improve it. (A while could be 1 or 2 hrs)
The reason for using those keys is because they are accessible by hand in the keyboard and they mean the intention of backward and forward.
According to the doc. a_user.key.handled=.T. is to make that key not function as originally intended.
Am I wrong here?
It seems that line has no operation at all. I was hoping that I was using it wrong and it will have proper syntax.
As I said the -> works, but some time gives me 2 advances in stead of the expected 1.
Could it that the pressing -> provides more that just forward or Alpha interpret it as more that one key?

[MikeData]

Re: a_user.key.value Does not work as I was hoping

Thanks Stan, I am using the doc sample. The difference is down vs right. left vs up in both lines
Notice commented 2nd option. I did tried the commented line and did not made any difference.
and it would have required to add 2 end ifs.
Am I missing something?

[Stan Mathews]

Re: a_user.key.value Does not work as I was hoping

Works for me.

a_user.key.value is tested for left or right
a_user.key.event won't ever be left or right or anything but up or down

The reason your right event processes 2 records is likely because it fires on right arrow being pressed (down) and right arrow being released (up).

[MikeData]

Re: a_user.key.value Does not work as I was hoping

Ah..... value -- event . That explains it, and yes IT WORKS. No extras & backward and forward.
Thanks for the correction and the interpretation Stan.

[MikeData]

Re: a_user.key.value Does not work as I was hoping

And for a case like space bar to move forward:
IF a_user.key.value = ui_keycode_normalize("{chr(32)}") THEN
a_user.key.handled = .T.
IF a_user.key.event = "down" THEN
parentform.fetch_next()
END IF
END IF