@mpergand Thanks I figured it out from that one. For now it seems to work just fine.
@JonB Thanks for the reply I toughed about that too but I'll try the eventfilter first.

@Axel-Spoerl That's what I was fearing, but thanks for confirming.

And I've found the point of this case: it was because of "inputMethodHints: "ImhNoPredictiveText" ". But why it adds english keyset to my virtual keyboard, I didn't catch it

Yes, something like an event filter. Or any other method that works

Hi,

Your code won't work, your QSqlDatabase object is invalid.

Please take the time to look at the code example in QSqlDatabase's documentation as well as the example provided.

It' also discouraged to store database object like that locally. QSqlDatabase allows for easy connection handling without the need for these local copies.

Hi,

for an integer input between 0 and 100 set the mask to "009". Thats all.

@subliminalman said in GamePad Input not Working:

gamepad

if you push your gamepad ,you will find the imputdata.yes, the example not work at checking the connect status.you can see my last answer.it can help you to have a code to work.

Hey @Wieland . Thanks for the help . It is working fine . ( i will customize it now to my needs )

Hi,

It might be not possible to insert a QChart object directly but a possible alternative might be to generate your chart, render it on a QImage and then put that QImage your QTextDocument.

Hope it helps

Looks like it might be a limitation/bug. The behavior is the same with 5.6

You should go to the bug report system to see if it's something known. If not please consider opening a new report providing a minimal compilable example (not just the code files) to reproduce the behavior.

i think the only things you need to do is open or shutdown bluetooth, find bluetooth devices and connect if needed. all the other things must have been done by the hardware vendor

@BluTiGeS
I'm using http://funq.readthedocs.org/ for something similar.

Hi Have you find any solution for this problem ?

That doesn't really help. I know the difference between the 2 devices.
The issue seems to be in the path and maybe the resulting timing Qt (QWS to be more precise) gets the XY position compared to the path over which it gets the click events. This seems not to travel the same way from DFB to QWS.
Still have no solution for this.

Sorry, I meant a more recent version of Qt Creator, as for Qt 4 the latest version is 4.8.7

@SysTech
Thank you for you reminding!