"With the OSX target you have to use KeyDown instead of KeyUp handlers."

"With the OSX target you have to use KeyDown instead of KeyUp handlers."
Is this a safe, known assumption and according to the guidelines?

Test app (Berlin) with one line in FormKeyUp event handler:

Caption := KeyChar;

Press key, then shift-key twice. (m M M)

Caption on Windows: 'm', 'M', 'M'
Caption on Mac: 'm', 'm', 'M'



My application uses key strokes to cycle through state.
Technically I will inc/dec an Integer property.
Initial value is 1.

normal key: inc (cycle forward)
shift key: dec (cycle backward)

If I want to change state like this:
2-3-4-3-2 //expected
m-m-m-M-M //keys pressed

I get
2-3-4-3-2 //on Windows
2-3-4-5-4 //on Mac

Found nothing in QP.
Any other problems related to this?
Known fix?
(I am using KeyDown and will be ok for now.)

(Another problem with KeyUp is the annoying sound produced by the arrow, home/end and prior/next keys.)

Comments

  1. Interesting:
    Key := 0; //in FormKeyDown
    will kill the arrow key sound on Mac !

    ReplyDelete

Post a Comment