diff options
| author | Oliver Wolff <oliver.wolff@digia.com> | 2013-11-19 12:47:03 +0100 |
|---|---|---|
| committer | The Qt Project <gerrit-noreply@qt-project.org> | 2013-11-23 19:58:34 +0100 |
| commit | d4c548ce5c0bd8a70c82ed082bc69fd41e9c47ed (patch) | |
| tree | 5162709d8246bc8a9d815030de829ddcb766ceb1 /qmake | |
| parent | a0e32cbf74e977cdb02defc91081f19b7746c392 (diff) | |
Fixed assert in Windows key handling
Certain key sequences (like press alt, press left, release left,
release alt) can cause an assert in qwindowskeymapper. This
behavior was introduced in change
I4f7709a90906b03f4504deea1ff5c361e9f94b3f (Fix virtual key
mapping on MS Windows). The place that seems to cause the new
behavior is changing the bitmask for obtaining the event's scancode.
With the changed bitmask releasing the alt key in the given
key sequence causes the WM_KEYUP event to trigger a WM_CHAR event
which should not happen there. To be honest I don't know how having
the extended bit inside the scancode fixes the behavior but it seems
to do and I could not find another place which might cause the
breakage.
Task-number: QTBUG-35005
Change-Id: Ia18c2681ea311196441a5cd15017e220ac095674
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Diffstat (limited to 'qmake')
0 files changed, 0 insertions, 0 deletions