I faced a very similar problem to this, so this was a very useful item. However, I found that I needed some further tweaks. For some reason, adjusting by the raw padding was not sufficient to ensure the text fitted in the box, so I fudged it by scaling by 0.9: font.pixelSize: 0.9 * (height - topPadding - bottomPadding) I also decided on a padding to height ratio of 0.15 but that was just my preference. One difference I notice between Windows and Linux is that Linux seems to be adding extra padding at the bottom despite the bottomPadding being reported as equal to the topPadding. I see this extra space with and without centred vertical alignment though maybe I saw a marginal improvement with the alignment set. Windows: Linux: Note the cursor height on Linux. I'm not sure how much one can read into it, but it seems to me that it does not seem to be aware of that space at the bottom of the text. A final observation is that the default padding was 6, independent of height (at least for the range I tried). This is pretty big for a moderate sized text field. As a relative newbie, I guess I wouldn't really have expected to have to mess with the default padding on a text field unless I had some special requirement. A lesson learned!

Was able to solve it by outcommenting selectionHandle in the custom keyboard style.qml file.

@red.green said in How to assign property values temporarily without breaking existing binding in qml?: How do I make sure that the previous binding is kept intact? Assigning a value breaks the binding - if it was not this way QML would be horribly broken ;-) There are a few ways around it, though. First, most obvious one - set the new value on the binding source. So if you have: Text { text: someProperty } Assign your temporary value to someProperty. You can add some code that will manage it's temporary nature there (onPropertyChanged or better in some object that holds the value of that property). Another way is to set up the binding using Binding element, disable it when Cancel is pressed, then enable it again once your temporary situation changes.

@Eeli-K sorry I have read your comment incorrectly :p

Hi, You need to send property like this: var loadwin = component.createObject(root, {someParameter: "Hello!"}) If you want to send property at any time (not only when your object will create) you need use alias property: property alias someParameter: textElement.text Text { id: textElement anchors.centerIn: parent text: "defaultParameter" } or signals. But I think alias property will be best way in your case. Hope this helps!

I solved that just removing the validators, but I don't know why it worked without the validator. Code below: TextField { id: numeroTelefoneTextField anchors.verticalCenter: parent.verticalCenter anchors.right: parent.right width: parent.width * 0.70 height: parent.height * 0.6 placeholderText: qsTr("Seu número") font.bold: true inputMethodHints: Qt.ImhDigitsOnly }

This has been fixed for Qt-5.6.1: https://codereview.qt-project.org/#/c/160147/

@CharlieG AFAIK inputMethodHints is related to the virtual keyboard. Depending upon the flags the correspoding keyboard will be invoked(like for eg. numerical keypad only or the both). Use validator instead. In your case for eg: TextField { validator: RegExpValidator { regExp: /[a-z]+/ //allow only lowercase alphabets } }