Red Hat Bugzilla – Bug 156572
patch breaks keyReleaseEvent()
Last modified: 2007-11-30 17:11:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3
Description of problem:
QWidget::keyReleaseEvent() is supposed to receive a QKeyEvent * which reveals which key was released to trigger the event. This works with an unpatched Qt 3.3.4, but in the Fedora version QKeyEvent::key() is always 0, regardless of what key was released.
This prevents from working properly any program which both needs to know about key releases and uses Qt.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Build the attached program: gcc -I/usr/lib/qt-3.3/mkspecs/default -I$QTDIR/include -L$QTDIR/lib -lqt-mt moc_test.cpp test.cpp -o test
2. Run: ./test
3. Focus the window.
4. Press and release your favorite key.
Actual Results: I like the spacebar, so what I see is:
Expected Results: I should see:
Created attachment 113912 [details]
moc file for test program
Created attachment 113913 [details]
I've now pinned down (roughly) which bunch of patches the problem comes from: If
you build without immodule support, keyReleaseEvent() works properly; otherwise not.
it's now fixed in qt-3.3.4-15. It will be available in rawhide soon.
For FC3-update, it will be available next week.
Many thanks for your report.
This seems to be broken again in qt-3.3.6-0.1.fc5 from updates-testing repo.
How exactly does it "seem" broken again?
Press ALT+F2 and then type program name (for instance "kate"). Hit TAB key to
mark "Options" button. Press SPACE.
With qt-3.3.6-0.1.fc5 (this time from updates repo) button "Options" is only
Downgrading to qt-3.3.5-13 resolves the problem - pressing SPACE key gives the
same result as mouse click on "Options" button.
I can reproduce this problem here. It's now fixed. The fix will be included
in next qt-3.3.6-0.2.fc5. I will build this new version for FC5 updates soon.
Thanks for your report.