I'm developing an application on a x86_64 tablet with MarbleWidget but could diagnose the same behaviour for marble-qt. I'm using Ubuntu 13.10 with Unity on the tablet. What I have: I have different QActions in a Menubar, a QTabWidget as the central widget of the QMainWindow and MarbleWidget as an Element of one Tab. As soon as the MarbleWidget becomes visible first time no touch input clicks on the application outside of the MarbleWidget are recognized anymore. It looks like normal mouse hovering instead of clicking. Pinch&zoom, dragging and clicking inside the MarbleWidget works. Clicking outside of the application works normal. Using an external standard mouse works normal too. Only the specific application with touch input are affected. Reproducible: Always Steps to Reproduce: 1. Create application with MarbleWidget and at least another button with a "visible reaction" like a test slot 2. Run application on touch device 3. Try zooming/dragging/clicking on MarbleWidget 4. Try clicking Button Actual Results: 3. works as expected 4. no "visible reaction"/clicked() signal of button not emitted Expected Results: 3. works as expected 4.clicked() signal of button emitted
Can you please add/attach a minimal example that demonstrates the problem?
Created attachment 85211 [details] Test case for the bug
marble-qt has the same problem. The whole settings and options on the left can't be clicked.
Calling setAttribute(Qt::WA_AcceptTouchEvents, false); on the MarbleWidget disables MultiTouch functionality but the rest of the GUI behaves normally now. This is only a workaround because pinch and zoom is absolute awesome to use with a map. So touch is somewhat broken. If touch is enabled all other GUI elements do not work. Disabling touch means loosing pinch&zoom... I enabled touch on the button from my test case which made the button work when MarbleWidget was touch enabled. but I didn't manage this for a QTabWidget. this is still definitly a big drawback on marble for touch devices!!!
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
I'm not using this any more and have no device to reproduce. With QML or newer Qt + Device drivers this is probably fixed. No idea though. Sorry for the trouble.