Yup, on 13.10. My ctrl+t know doesn't work. Sooo i must have messed up testing it :). So yes there is a problem there.
Really im just wondering what use to happen, if this is a regression. As I see 3 cases, and 2 different ways to handle this.
1) You are using a standard qwerty latin keyboard with all the keys in the correct spot.
2) You are using a different layout where they keys (such as 't') may be in different locations.
3) You are using a language where such a key does not exists (such as 't').
The two ways to possibly handle this, as in case 1 there is no need to change how we handle it.
If case 2, use the new location of the key if it has moved.
If case 3, use the keycode of the key it self when no such key exists.
Not entirely sure what the approach should be and would like to discuss this a bit more before heading down an implementation.
Yup, on 13.10. My ctrl+t know doesn't work. Sooo i must have messed up testing it :). So yes there is a problem there.
Really im just wondering what use to happen, if this is a regression. As I see 3 cases, and 2 different ways to handle this.
1) You are using a standard qwerty latin keyboard with all the keys in the correct spot.
2) You are using a different layout where they keys (such as 't') may be in different locations.
3) You are using a language where such a key does not exists (such as 't').
The two ways to possibly handle this, as in case 1 there is no need to change how we handle it.
If case 2, use the new location of the key if it has moved.
If case 3, use the keycode of the key it self when no such key exists.
Not entirely sure what the approach should be and would like to discuss this a bit more before heading down an implementation.