Ok, thanks a lot! Marked as solved!

QComboBox {background-color:rgb(190,190,190);color:black;padding-left: 10px;padding-right: 30px;border-style: solid;border-width: 0px;} "padding-left: 10px;" the padding will shift the combo-box displayed content form the left edge QComboBox::drop-down {subcontrol-origin: padding; subcontrol-position: top right;width: 40px;border: 0px ;} "subcontrol-position: top right;" and the above will position wot text to the right. Hopefully this helps.

@Rohith instead of converting the unicode string to the escaped characters send it directly in binary form. When you have a QString already you can call QString::toUtf8() and send the returned QByteArray directly. On the client its enough to do QString::fromUtf8( receivedUtf8ByteArray.constData() ) It depends how you implemented the transfer. But theoretically it should be enough to replace your unicode escaping code on the server with this approach.

I can't say that I understood your code, but if you'll change the return value of your reading method (read(), I presume) to QStringList, then you can display it with ListView in QML like this: ListView { //Layout.preferredHeight: childrenRect.height model: myFile.read() delegate: Text { text: modelData } }

Please report a bug at bugreports.qt.io.

@Qjay You can get text like this, Create instance of search.qml means like Search(this is your search.qml file instance, first latter should be capital of your qml file) { id: searchText } 2 In search.qml file create property like property alias Name_of_variable(like textOfSearchField): id_of_textfield(search_text.text) Now wherever you want to use, can do like this. searchText(id_of_instance).Name_of_variable You will find exact value as you passed in search.qml file

You can use QSqlQuery to run the select statements and loop the resultset with next() like in VRonin´s example. If you comma seperate the columns like in VRonin´s example you can open this file in excel. One more option, if your on windows is to use ODBC Excel Driver to generate the Excel file. With this you can use QSqlQuery to create tables and insert rows.

The application runs in RAM, with all the qt dll useful for the deployment. Is it possible that a RAM corruption can cause a problem related to interface (font corruption, background image corruption...)? Thank you

Hi Have a look at http://doc.qt.io/qt-5.5/qtextobjectinterface.html#details http://doc.qt.io/qt-5/qtextobjectinterface.html and the "Text Object Example" It seems possible to create your own widget to support such feature but I have no tested it and do not know if object would receive events. also docs says "Copy and Paste operations ignore custom text objects."

Aliasing problem ?

Ok, so what happened before is that the item you added was destroyed before it could be shown

You need to add the module path to QML import path. You can do that in 2 different ways: Add "<path-to-qml-material>/modules" to your QML2_IMPORT_PATH env var. Or add it in your main.cpp using engine.addImportPath("<path-to-qml-material>/modules/");

So as it turns out, compiling Qt 5.5 from git seems to solve this problem. I tried my demo program, as well as Maroon, and both display text by default (without having to set renderType to Text.NativeRendering). Dang it. That's what I get for trying a pre-release version. Thanks for the suggestion.

@JackCWallace You need to set an visual parent to the newly created item using setParentItem. For this you will have to create a QQuickItem ofcourse.

My problem is image delegate only. I found addiotional regularity: problematic delegates have the same picture as last top delegate hidden during scroll down within ListView. It seems scrolling out delegate from visible area forces it's image repaint in other delegates, which are in visible area. This repaint seems to hide the text element, declered with z-order above the image. Reset the visible property (visible=false, visible=true) at end of each scrolling (using onMovementEneded) solves the problem. But, i don't want to pay the repaint price of such solution as my application is running on embedded device.

I found a workaround: Define environment variable within Qt application startup context: QML_USE_GLYPHCACHE_WORKAROUND = 1 Look on this topic: https://forum.qt.io/topic/39803/font-rendering-bug-on-some-android-devices/7

Fixed by using a different font.