Maybe it is not the fault of QtQuick ->
Please try environment QT_OPENGL=angle - there so many problems with the OpenGL driver on windows, yes even in 2018 maybe angle should be again the default (it was it for some versions) because there are so many issues with it.

http://blog.qt.io/blog/2017/01/18/opengl-implementation-qt-quick-app-using-today/

and even for QtCreator we are thinking about going back to the angle opengl wrapper:
https://codereview.qt-project.org/#/c/223028/2//ALL,unified

You have 2 versions of TextArea in QML. Which one are you using ?
Do you mix Controls 1 and 2 ?

Controls 1 have a specific property tabChangesFocus :
http://doc.qt.io/qt-5/qml-qtquick-controls-textarea.html#tabChangesFocus-prop
I did not succeed in making it work right now, though…

But this works :

Row { TextArea { id: mytext width: 100 height: width focus: true Keys.onPressed: { if (event.key == Qt.Key_Tab) { event.accepted = true; mytext.append('\t') } } } TextArea { id: mytext2 width: 100 height: width } }

Pay attention where you put the Keys attached property.

With Controls 2 :
The previous solution does not work, but it appears that the default behaviour is what you're looking for : mytext keeps focused on when tab is pressed, and a tab is inserted in the text.

Row { spacing: 10 Rectangle { id: rect1 width: 100 height: width border.width: 5 TextArea { wrapMode: TextEdit.WrapAnywhere id: mytext focus: true anchors.fill: rect1 } } Rectangle { id: rect2 width: 100 height: width border.width: 5 TextArea { wrapMode: TextEdit.WrapAnywhere id: mytext2 anchors.fill: rect2 } }

@Bits-n-Flips said in Combobox with ListModel and PyQt5:

@J.Hilk
Well, I don't want to hide them. I can just delete entries (or append them too), that works fine. What I'm trying to do is disable the entries; gray them out and make them unselectable by the user, I don't want to hide them because I want to show the user that in another version these entries will be usable.

Also if I set the ListElement height to 0 or clip to true; nothing happens. It still renders and I can still see the entry.

Ok I see, I wrongly interpreted your intensions than.
All QML items have the property enabled its set by default to true and you can disable the Item with that. If you don't make your own Style, than the Item becomes grey andI believe all interactions are disabled

@Jman006

Ok I made progress. This CMakeLists.txt is hardcoded for the iOS simulator. When I select the simulator in XCode, everything links properly. I still have a runtime error, but that is a different issue.

I'm still working on getting the both simulator and actual hardware versions to build. I'll post back the results.

@TM9412 said in How I will create QRcode in qt-apps/neptune-ui.git ?:

I follow the same procidure

Could you please describe what procedure is this? So to understand why it isn't working as expected for you with neptune-ui

Basically I guess you need the QZXing library built for the platform you'll be running this Qt app, and then you need to register QZXing as an image provider with the QML engine via addImageProvider method.

Thank you for the effort.

The problem is that this "otherObject" is not a QQuickItem, and I do not have a way to get it in QML. This "otherObject" is an item of the model itself.
So there is no point in initializing it in QML, like you did with

OtherObject{ id: obj2 }

http://doc.qt.io/qt-5/model-view-programming.html#creating-new-models

The ideal would be to get the pointer to the customQQuickItem instance in c++.
I'm thinking about setting a role and pass "this" in QML to that role.
That way I can access the instance in C++ side. But I'm not sure it would work... And I don't know how to access the current item in the model being built in QML side.

Update: I can access the QQuickItem now.
Though the method is not so covenient. Not something that I've seen, at least.
In my modelItem, I keep a *customQQuickItem pointer. Set to null in constructor.
Then, in QML:

customQQuickItem { id:customItem Component.onCompleted: { customItemRole = customItem } }

Then, on the c++ side. The model handles the role, when QML sets it, and it updates the pointer.
And now, I have access to the custom QQuickItem

@J.Hilk
Thank you , i got it

I solved, do not forget to give parent item to createObject.

Please check my example using QML GraphicalEffect to get the starting point.
QML Glow Rect

@J-Hilk thank you. It is more than enough for me to study with your code. Kind Regards

@Alien said in Export enum from C++ into QML:

Thank you for your solution that works fine but I think that I've to use both registration please look at the below code

engine.rootContext()->setContextProperty("COBJECT",&test); qmlRegisterUncreatableType<C_TEST >("CppEnums",1,0,"Enums","Enum is not a type");

Since I need the mode variable (this variable will change time to time)

you need the contxtProperty too, the qmlRegisterUncreatableType just makes your Enum(-class) available to your qml files you still need a reference object from your cpp-backend.

does this usage have any problems?

I don't think so, I use it the same way.

@DuBu said in How to precisely center and adjust the size of any text ?:

Your description and code sample are rather big so I try to answer your question more generally.

Sorry, for some reason, I missed your answer.
The code sample is meant to be cut and pasted in your Qt Creator and just work. You have to get the fonts first in order to reproduce the same images, but using other fonts and characters may also work in demonstrating the problem (the "Cg" example should be easy to reproduce with any font).

In summary, you want a text to fill it's parent and if one direction is smaller then its parent it should be centered in that direction?

Yes.

Does the following do what you want?

Rectangle { Text { anchors.fill: parent fontSizeMode: Text.Fit font.pixelSize: 10000 // maximum height of the font minimumPixelSize: 8 // minimum height of the font horizontalAlignment: Text.AlignHCenter verticalAlignment: Text.AlignVCenter } }

No.
I use this kind of parametrization it in the provided code.
It fails in both aims you put in your summary.

Well, the Rationale here is that Qt is extensively used on server side (Core, Network), and and there are no known issues we have related to Qt on that side. I would now add a small, not-so-important UI program to that.

For the server people, updating to a newer version of Qt incurs costs (risks of regressions / new bugs, testing) but bring no apparent benefits (none of the new features is needed, no bugs of interest have been fixed).

I have been offered to run my little tool on a separate Qt version, so I might have solved my problem that way.

Hi thanks for your help.
I had earlier written the method as :

category.onAccepted : { console.log("Print onAccepted"); }

The below code solved the issue.

Connections{ target: category onAccepted : { console.log("Print onAccepted"); } }

hi @wost,

have you already searched for input mask and input validator?