This is very od, ill explain it the best I can.
I'm watching for keypress events. See below of strange results.
1) if I press a key on the stage event Triggers
1) if I press a key on a grid event Triggers
1) if I'm in edit mode on a grid only the 5th key press ( letter or number ) fires the browser keypress event.
a) double click to edit a cell
b) press the letter a ( not event fires )
c) press the letter b ( not event fires )
d) press the letter c ( not event fires )
e) press the letter d ( not event fires )
f) press the letter e ( event fires )
Any ideas? I need my even to fire after any keypress.
Hello Sean,
You can explain it the best with a sample :)
On which element you're looking for the keypress? The behavior you're observing may be caused by the grid updating not bubbling the keypress event in some cases i.e. calling event.stopPropagation().
Again, a sample will explain it the best.
Thanks,Martin PavlovInfragistics, Inc.
No I dont do any stops or return false's. The code is quite involved to the point I can not example it. It sounds to me like you understand my issue. The only two events in update I use are editCellStarting and editCellEnded. I put alerts in both to see if they where firing and when I double click editCellStarting fires as it should but pressing letters does not fire these events.
I have a few other elements on the page like a tree with a text box in it and it works as it should. So I know its the grid that has the problem. The only place the event has this problem is in a cell edit mode. Even pressing on a grid header works correctly, as if the edit mode may be to blame?
re-cap: Once in edit mode my keep press event does not fire until I type the 5th character.
In your experience would you suggest any debug tools to catch the problem?