Mobile and Embedded

Call configure with -v, you should have some more details on what fails

Hi, Did you try running your application through the debugger ?

Hi SGaist, found the reason for that. The handler was ok, it was an other parameter i was passing to an ios call which made me believe that this handler was wrong. thx, patrik

@sierdzio Thank you. This is a exciting news for me.

update: Found this thread that there is no available text/glyph node yet for text rendering on the scene graph node. http://comments.gmane.org/gmane.comp.lib.qt.user/13735 It was suggested (but not ideal) to draw text using QPainter on QImage and show on texture. Any advise how to convert the image into texture? I can't find any example. Thanks.

@SGaist Guess this is my wake up call to try QML seriously :-) @TobyYi is your 多多指教 app opensource? I couldn't see the info about that on your page.

What does a run through the debugger tell you ?

@phil999 I too have struggled with getting the Tslib touchscreen implementation to work. I've spent a lot of time sprinkling print statements around in the Qt code figuring out what is going on. What I've learned is this: Tslib and Evdev are separate implementations that are NOT equivalent. The Tslib implementation was developed for single touch (generally resistive) touchscreens while the Evdev implementation was developed for multi-touch (generally capacitive) touchscreens. For single touch screens, every action possible can be characterized as an equivalent mouse operation and that is what Tslib does. (Note that the Tslib plugin calls handleMouseEvent, not handleTouchEvent). Conversely the Evdev implementation does handle multi-touch which has no mouse equivalent so Evdev characterizes the touchscreen events as touch events. You MUST get your touchscreen properly calibrated so that the coordinates are within the screen dimensions. Mouse events will only be reported to an object if they are within the object. Try recalibrating the touchscreen (ts_calibrate) and then run ts_test to be sure the touchscreen operation is correct. (We found that some versions of ts_calibrate don't work correctly and made some changes in the code ourselves.) Event type 50 is a notifier event that I believe is triggering the QTsLibMouseHandler::readMouseData(). You can ignore these. Your event filter should be looking for Mouse events. Probably these will be GraphicsSceneMousePress, GraphicsSceneMouseRelease, GraphicsSceneMouseMove, GrabMouse and UngrabMouse. (But this is object dependent.) I was using the qtbase/examples/touch/knobs application for test and debug and in the Knob::sceneEvent() function in knob.cpp, I changed the case statement to look for those 5 events. On a touch-drag-release I typically see the following sequence: GrabMouse GraphicsSceneMousePress A variable number of GraphicsSceneMouseMove GraphicsSceneMouseRelease UngrabMouse Be sure to intercept these events and not call the default QGraphicsItem::sceneEvent() handler. It will inhibit seeing all of the above events except the initial GrabMouse and GraphicsSceneMousePress Hope this helps!

No, didn't help. fi.pointSize returned even smaller value: 12

@micdoug said: In Qt Indie Mobile license are there any additional qt quick controls? Or the only difference is on the publish to third party stores. There are no additional Qt Quick controls. See http://www.qt.io/download/ for the full list of differences.

Hi and welcome to devnet, What version of Qt 4.8 are you currently using ?

I know this thread is old, but some of us are still stuck with QT 4.8.4 (QWS) in embedded. I spent some time trying to figure out how to selectAll on a lineEdit that was setup via a UI file. I tried the following, but it didn't work . ( note it does work when I build for desktop ) ui->lineEdit->selectAll(); ui->lineEdit->setFocus(); Then I noticed If I pressed the line edit then ran the selectAll() it worked. So if you force a mouse press event for the widget, it forces focus and hence will let you selectALL(). QEvent eventPress( QEvent::MouseButtonPress ); QEvent eventRelease( QEvent::MouseButtonRelease ); QApplication::sendEvent( ui->lineEdit , &eventPress ); // simulate a mouse press QApplication::sendEvent( ui->lineEdit , &eventRelease ); // simulate a mouse release ui->lineEdit->selectAll(); This worked for me, I hope it can get someone else out of a bind too. I'm posting this because I didn't see any other examples of people with this work around.