there should be a work around
ok this is untested but this should give you a starting point. might be a
messy workaround.
this may not be a solution but a step to identifying one.
try something like this
var keyhit = new Array(); // hold an array of keyvalue
var lastkeyhit = new Array(); // hold an array of keys hit last in order
var index = -1; // index of key hit last
$("#myid").keydown(e) {
keyhit[e.which] = 1; // assign the key code of the key down as the array
index
index++; // increment index
lastkeyhit[index] = e.which; // assign order of keys hit
});
$("#myid").keyup(e) {
for(var i = 0; i < index; i++) { // for loop through array
if(e.which = lastkeyhit[i]; // if key is logged
keyhit[e.which] = 0; // set its state to 0
Array.remove(e.which); // remove it from the list of key hit last
index--; // decrement index as a log is removed.
}
});
// this isn't really tested but it should help you keep track of keys hit in
order and in which order they were released
On Sun, Jun 14, 2009 at 9:27 PM, Rune <a...@rdfined.dk> wrote:
>
> So is the answer, that this is a jQuery issue?
