onKeyDown() for KEYCODE_BACK supressed
Micke Prag
micke.prag at telldus.se
Wed Jan 9 17:10:03 UTC 2013
Hi,
Thank you for your reply. After reading that thread I still cannot understand why onKeyDown() is suppressed. Is there something that won't work if Qt get both keyDown and keyUp for the back button like any other button?
For instance, the volume keys will be sent to Qt as both onVolumePressed and onVolumeReleased.
I have a patch ready for going upstream but it depends on getting the onKeyDown event for the back button. I am wondering if my patch breaks something by allowing this signal to pass through?
Regards
Micke
> Hi,
>
> Check this thread https://groups.google.com/group/android-qt/browse_thread/thread/a5beee9f561ef763/a3fa2791fbf88c37
>
> Cheers,
> BogDan.
>
>
>
> >
> >Hello,
> >
> >Looking through the code for QtActivityDelegate.java I find the following rows in the onKeyDown()-method:
> >if (keyCode != KeyEvent.KEYCODE_BACK)
> >QtNative.keyDown(keyCode, c, event.getMetaState());
> >
> >Source: https://qt.gitorious.org/~taipan/qt/android-lighthouse/blobs/beta2/src/android/jar/src/org/kde/necessitas/industrius/QtActivityDelegate.java#line472
> >
> >
> >So basically the onKeyDown event for the back button is suppressed from the application. What is the reason for this?
> >The onKeyUp event is not filtered, only onKeyDown.
> >
> >I am working on an implementation to ease up the back button handling, especially for QML-applications and this filters the event I am interested in.
> >
> >Regards
> >Micke
> >_______________________________________________
> >Necessitas-devel mailing list
> >Necessitas-devel at kde.org
> >https://mail.kde.org/mailman/listinfo/necessitas-devel
> >
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/necessitas-devel/attachments/20130109/01aa73fe/attachment.html>
More information about the Necessitas-devel
mailing list