QML and Qt Quick

@GrecKo Nice and good example! I can solve my problem. Thanks.

not that for a single parameter you can get rid of the parenthesis, mouse => { ... } works

It works ! Thanks (I don't understand it either...)

@timob256 you mean this? https://doc.qt.io/archives/qt-5.11/qtquick-qmlmodule.html

That's how font works in every UI system, there is a fallback behavior. As for why there is both font.family and fontInfo.family, it's because it makes developers life easier. You can actually see if the chosen font differs from the one that was set without having to store the expected font somewhere else. For the font family you can also gives a very vague one like "serif", "sans-serif", "monospace" and seeing what the font matched with fontInfo might be important. It would be weird to do font.family = "sans-serif"; and then getting "DejaVu Sans" back when querying font.family, wouldn't it? QML is declarative, so making font.family a function won't be very practical and give much advantages. You already have your feedback in a declarative way, I really don't see how an imperative API would be any better? Do you have a pseudo code example of what your perfect API would look like?

Use topMargin property of Table View.

I figured it out. For anyone who's interested. If you set the visibility of the contentItem to be: visible: theListView.contentHeight > theListView.height that should do the trick.

This is an annoying problem and I'm struggling with it at the moment. Did anyone manage to find a proper workaround to it?

@Cyrille-de-Brebisson Q_PROPERTY(QList<MyObj*> liste READ getliste NOTIFY listeChanged) now emit the listeChanged signal everytime you change the list If you would implement a QAbstractListModel subclass you would have more control of rearrangements etc.

@Tee_ normally a pro file results in a separate target (executable or library). Even if you "combine" them with a subdirs project. So your AppUi project must link against the AppLib

You could draw a line on top. Not ideal. Edit: Width of 1 rect with border.

@caicx said in Conditional Import: import QtGraphicalEffects 1.0 // Required by Qt 5.x.x vs import Qt5Compat.GraphicalEffects // Required by Qt 6.x.x yes and? Since the major version of Qt has changed you should also advance with your project, instead of importing a compat module of a previous version for the whole lifespan of Qt 6. The compat module is intended to be used as a quick solution until the porting of your application to Qt6 has finished

@jsulm - Thank You

@J-Hilk No, I haven't considered it because it has been working fine until now. Sorry, I made a mistake, it's "5.15.2" to be exact. I created a new project with the exact same settings and the exact same code, and it worked. Was there a problem with the settings that I missed somewhere?

Didnt know about breaking bindings yet and I feel like I dont understand the code onActivated well. What does => means / how it's named? Currently the custom item is defined like this: LeftBind { id: enabler x: 291 y: 15 keyName: keyTranslator.getKey(Config.enabler) //Config.enabler is vkey (int), this function converts it to readable string (for example from c++ vkey 0x10 to "ALT") onAccepted: { var a = keyTranslator.getCode(keyName); // from string to vkey if(a === 404){ askForKey() } else { Config.set_enablerBtn(a) } } }

@JoeCFD I was working on other stuffs but now I remember why I can't override QQuickItem update() method... it is a non-virtual slot, so it can't solve my rendering issues. I am still looking for a solution ...

@jeanmilost Your logic seems to be correct. What you have to do is to move the re-calculation of Scrollbar size & position to the Rectangle rcPageContainer because you are applying scale for that. Rectangle { id: rcPageContainer objectName: "rcPageContainer" ... /// called when page viewport width changed onWidthChanged: { sbHorz.size = rcPageViewport.width / rcPageContainer.width sbHorz.position = Math.min(Math.max(sbHorz.position, 0.0), 1.0 - (sbHorz.size)); } /// called when page viewport height changed onHeightChanged: { sbVert.size = rcPageViewport.height / rcPageContainer.height sbVert.position = Math.min(Math.max(sbVert.position, 0.0), 1.0 - (sbVert.size)); } }