@Kent-Dorfman I'm sorry, but I steel don't get it...I have two physical monitors each of which is 1280x1024px. If they span into one display I should get a screen with 1280x2048 resolution, shouldn't I? But my screens list contains one an entity with {0, 1024, 1280, 1024} rect for available geometry. I can test what returns availableVirtualGeometry method tomorrow in the office, but no matter it does I can't find a way to render a GUI on the second physical monitor properly.

@morte

ApplicationWindow { Item { id: banner x: 0; y: 0 width: parent width; height: 50 } Item { id: content width: parent.width anchors { top: banner.bottom bottom: parent.bottom } } }

Do you have that error on both platforms ?

By the way, can post a minimal sample code that shows this behaviour ?

@romsharkov You may use a custom theme to turn off the ActionBar.

Example:

quickandroid/apptheme.xml at master · benlau/quickandroid

quickandroid/AndroidManifest.xml at master · benlau/quickandroid

Document:

Complete Guide to Making a Splash Screen for your QML Android Application — Medium

I have been looking into this myself, with no conclusive information on how to reliably accomplish this. It feels like Qt 5.6 ought to automagically do the scaling for you; I intend to post a new question in this forum asking about this. In the meanwhile, the first part of this video will be of interest to you:

https://youtu.be/nNyhsdX6BsI?t=6m24s

There is code at 06:24 that extracts the dpi value from the Android framework. Maybe that will work better, I have not tried it myself.

Issue resolved by configuring qt4.8.6 with configure option as follow ::

sudo ./configure -prefix /usr/QT4.8.6 -opensource -embedded arm -depths all -xplatform qws/linux-imx6-g++ -release -shared -fast -pch -no-qt3support -qt-sql-sqlite -qt-libmng -qt-libjpeg -qt-zlib -qt-libpng -qt-freetype -no-openssl -nomake examples -nomake demos -nomake tools -optimized-qmake -no-phonon -no-nis -no-opengl -no-cups -no-xcursor -no-xfixes -no-xrandr -no-xrender -no-xkb -no-sm -no-xinerama -no-xshape -no-separate-debug-info -no-qvfb -qt-gfx-linuxfb -no-gfx-qvfb -no-kbd-qvfb -no-mouse-qvfb-qt-kbd-usb -confirm-license -svg -webkit -javascript-jit -script -scripttools -declarative -declarative-debug -multimedia -exceptions -xmlpatterns -plugin-mouse-tslib -qt-mouse-tslib -qt-freetype -qt-gfx-linuxfb -qt-kbd-tty -qt-kbd-linuxinput -qt-mouse-linuxinput

option -depth all :: fix the issue

Compiled and rebuilt with Qt5.5.0 (beta). Unfortunately, the problem persists.

Hi and welcome to devnet,

Do you mean showing a fullscreen widget or just a decoration-less widget ?

@RDiGuida To add to @Mario84's answer, QString is Qt based class and your using standard c++ API's to print it which it doesnot understand. To print values of pure Qt based API's you can use qDebug().
Eg:

QString dt ((dates[0]).toString()); qDebug() << dt;