[scribus-dev] Who's eating Shift+Tab?

[Elvis Stansvik]

2011/8/18 Craig Bradney <cbradney at scribus.info>:
> On 18/08/2011, at 17:02, Elvis Stansvik <elvstone at gmail.com> wrote:
>
>> False alarm,
>>
>> I found the reason.
>>
>> For some ungodly reason Qt does _not_ send an event with
>>
>> key() == Qt::Key_Tab
>> modifiers() == Qt::ShiftModifier
>>
>> when Shift+Tab is pressed. Instead it sends one with
>>
>> key() == Qt::Key_Backtab
>> modifiers() == Qt::ShiftModifier
>>
>> (Note the Key_Backtab).
>>
>> Confusing!
>>
>> Elvis
>>
>> 2011/8/18 Elvis Stansvik <elvstone at gmail.com>:
>>> Short question:
>>>
>>> Anyone know what in Scribus might prevent Shift+Tab from reaching my
>>> table edit mode keypress handler?
>>>
>>> Just Tab reaches it fine, but Shift+Tab is filtered somewhere higher up.
>>>
>>> I've grepped for all occurances of "Key_Tab" and "ShiftModifier" but
>>> so far I've been unable to find where it is caught :/
>>>
>>> If anyone has an idea off the top of their heads, I'm idle ears.
>>>
>>> Cheers,
>>> Elvis
>>>
>>
>> _______________________________________________
>> scribus-dev mailing list
>> scribus-dev at lists.scribus.net
>> http://lists.scribus.net/mailman/listinfo/scribus-dev
>
> Ah
>
> Qt doesn't send the "base" key plus modifier , it sends the final key plus modifier. This means shift tab can produce different results on different keyboard layouts

Right. In a way it makes sense, but caught me up for a while.

Elvis