@Pablo-J-Rogina Hi, thanks for your quick reply. It does nothing at all unfortunately

@sierdzio thanks a lot for the pointer and example document, I will look into this

Hi, You will have to use the corresponding private module in your project.

Are you looking to do error-checking and error-prevention by ensuring (before "shipping" an application) that all your C++ types that should be registered are, indeed, actually properly registered? If that is your goal, then I commend you. I am interested in that topic as well. So far, I have been able to greatly increase detection of many such issues using a combination of: total ban on "qml warnings". (things that qml prints as "warnings" tend to be what I consider fatal bugs). launch the application during automated testing use automated scripts to scan the output of the launched application for any forbidden output such as "unregistered datatype" and "failed to load component" The ban on warnings that I mention in point (1) is achieved by installing (in C++) a Qt custom message handler to spy on all logged messages and abort if any messages are "warnings" emanating from a qml file: https://github.com/219-design/qt-qml-project-template-with-ci/blob/4d81552d77/src/app/qml_message_interceptor.cc#L44 Launching the application during C.I. on a headless machine is done with Xvfb: https://github.com/219-design/qt-qml-project-template-with-ci/blob/4d81552d772c32b7d62edb4b4f0f678ca92bed4f/run_all_tests.sh#L50 The warnings-ban could be used on any platform. The Xvfb automation, to my knowledge, would be limited to Linux applications. Therefore a parser-based detection system could be a more cross-platform portable solution. If you come up with a parsing-based solution, I'm sure that I and many other users that combine C++ with QML would be happy to try out your solution.

@SGaist And we have a winner ! That was the issue, thank you :)

@Babs SpinBox is for integers, not floating point numbers. But you can use floating point numbers as shown in the documentation: https://doc.qt.io/qt-5/qml-qtquick-controls2-spinbox.html In the same manner, SpinBox can be customized to accept floating point numbers: SpinBox { id: spinbox from: 0 value: 110 to: 100 * 100 stepSize: 100 anchors.centerIn: parent property int decimals: 2 property real realValue: value / 100 validator: DoubleValidator { bottom: Math.min(spinbox.from, spinbox.to) top: Math.max(spinbox.from, spinbox.to) } textFromValue: function(value, locale) { return Number(value / 100).toLocaleString(locale, 'f', spinbox.decimals) } valueFromText: function(text, locale) { return Number.fromLocaleString(locale, text) * 100 } }

Alright after some research I probably found a workaround to fix this. I got help and inspiration here. The problem is that sometimes when the elements are stored in containers such as ScrollView the z-order thing doesn't work well plus the container can catch mouse event not allowing it to propagate to the helper MouseArea. In such cases all the problematic elements need to contain TapHandler which allows to catch the click event and do custom action. So for example: ScrollView { TapHandler { onTapped: outFocuser.forceActiveFocus();} } In this way no z-order tricks are needed nor the onActiveFocusChanged property in TextArea.

@J-Hilk thanks you. The list was empty.

Thanks you all. I'll try to do it.

@Babs Anytime. Please don't forget to mark the thread as "solved".

@SyntaX said in Timer stops/pauses if Activity is suspended in Android: Do I just send an Email to android-development@qt-project.org and everyone who is subscribed gets the message? Seems a bit of a overkill like @everyone to me? No problem, you first have to register to the mailing list, and then you can send emails to it. This is the Qt-Android developers mailing list. So your mail will be received by each member. That's the way mailing lists works ;-) You can also try to contact BogDan Vatra from KDAB, which is the main developer of Qt/Android

As I mentioned, I would like to play with any style, so I guess I'm not able to hardcode use of Material style.

@J-Hilk I managed the required behavior, somehow. By blanking the key value: stg.setValue("step_1", "") then scanning the keys, which have non-empty value, and skipping the empty ones. I'll file a bug, cause I think it's a needed method! By the way, thank you all

use file selectors for showing completely different UI https://doc.qt.io/qt-5/qfileselector.html#adding-selectors You can also add extra selectors at runtime for custom behavior. These will be used in any future calls to select(). If the extra selectors list has been changed, calls to select() will use the new list and may return differently.

@sierdzio No problem! Will keep on searching. Once again, thanks for your help! Best wishes, Henderson

I fixed it - so this is for anyone else having a similar issue. I'm not sure why this happened but in a RowLayout, I had a button that used Layout.prefferedWidth + Layout.prefferedHeight. relative to its parent - and this caused the error. Deleting the lines worked, but when I was checking with just 1 of them, I got a 'binding loop' error for the prefferedWidth - I'm guessing multiple of these caused it to crash.

@fcarney I am new to Qt so don't anything about Loader and Can you please take a look at this question too: https://forum.qt.io/topic/111852/inconsistency-between-model-and-view-while-updating-qsqltablemodel-cell

Did you saw the third argument of the signal ? The one you are currently not using in the code you provided. It's the one containing the custom roles.

@SGaist @Christian-Ehrlicher How would I let the view know about the data change ? And I would like to mention I am displaying the list of users with UserRole like this: QVariant UserModel::data(const QModelIndex &index, int role) const{ QVariant value; if (index.isValid()) { if (role < Qt::UserRole) value = QSqlQueryModel::data(index, role); else { int columnIdx = role - Qt::UserRole - 1; QModelIndex modelIndex = this->index(index.row(), columnIdx); value = QSqlQueryModel::data(modelIndex, Qt::DisplayRole); } } return value; } QHash<int, QByteArray> UserModel::roleNames() const{ QHash<int, QByteArray> roles; for (int i = 0; i < record().count(); i ++) { roles.insert(Qt::UserRole + i + 1, record().fieldName(i).toUtf8()); } return roles; }

Hi I have not seen steam on linux , however they might have use https://en.wikipedia.org/wiki/Client-side_decoration or something similar. or have hand made it. While this works ok for win https://github.com/dfct/TrueFramelessWindow I have not seen one for linux. Maybe due to all the different managers. Short story is. Qt do not draw the title bar so one can either totally fake it and draw all - and handle all min/max resize etc by manual code or if the Desktop/Manager supports it, use direct api extensions.

@Ahti Dunno, but why don't you start by showing us/yourself the return values of the calls to user_model.setData(user_model.index(...? What's the result for you of: https://doc.qt.io/qt-5/qsqltablemodel.html#editStrategy ?

@fcarney Easy as that. This works perfectly fine with just a ListView. I added a ScrollBar to it and I have the same without any binding loops. Thanks!

hi just move the Layout.fillWidth: true from phone to p_label RowLayout { id: p_layout width: parent.width Label { id: p_label text: "Phone: " font.pixelSize: 13 Layout.fillWidth: true//<< } Label { Layout.alignment: Qt.AlignRight // this doesn't align to right id: phone text: "987654321" font.pixelSize: 13 } }

You can get StackView instance from Profile.qml quite easy, using StackView attached properties. Define new property at your StackView: StackView { id: home property var modeldata: null // Define StackView property initialItem: Pane { ... ListView { ... delegate: SwipeDelegate { ... swipe.onCompleted: { if (swipe.position > 0) { home.modeldata = model; // Set StackView property home.pop(); home.push("Profile.qml"); } ... } ... } } } } And then at Profile.qml you can easily get attached StackView property: Pane { id: profile ... Button { ... text: "Delete" onClicked: { let modeldata = profile.StackView.view.modeldata; // Accessing StackView property via attached properties if (modeldata !== null) { user_model.removeRow(modledata.index); } ... } } } In this case you do not need workaround with helper row. Also if you need some objects like your helper - better way is to use QtObject rather than visual 'invisible' object.

@TMJJ001 hi the canvas content is generated programmatically, i'm not sure you can do it in the Designer

@jsulm said in switch button problem! qml: @imhs It is, see "The following members are inherited from Item." section in the link you posted. Thanks for your help. I saw it.

Thanks guys! Im on Qt 5.10, that explains why the "=>" is not working. Had not known about the old style syntax. Settings this to closed.

Hi @Kyeiv, I just did a quick test application and it worked for me: main.qml import QtQuick 2.9 import QtQuick.Window 2.2 import "someJSscriptFile.js" as Jss Window { visible: true width: 640 height: 480 title: qsTr("Hello World") Rectangle { id: rect color: Jss.getCurrentColor() anchors.fill: parent } } someJSScriptFile.js function getCurrentColor() { return __getColor(rect.currentValue) } function __getColor(value) { if (rect.pressed) { return "grey" } if(rect.activated === false) { return "white" } if(value ===0) { return "red"; } return "green"; } Is the variable "control" defined in your QML? Or what are you trying to use it for?

@Ahti Perhaps not relevant, but can't help noticing: your removeRows and its call to beginRemoveRows() correctly allows for multiple rows, but your call to response = model->removeRow(first, QModelIndex()); only allows for one row. That's works for your del_row(), but not in general. I don't suppose fixing that changes behaviour?

I'd be careful just because of my own assumptions / experience, it sounds like you're setting up a landmine for later, I don't know because I just skimmed your issues, I can't tell enough for a proper context but I can recall the bug report that I found when I did. You might find this useful too: https://bugreports.qt.io/browse/QTBUG-43230 Ulf Hermann added a comment - 18 Mar '19 9:19 PM Note that exposing objects that live in a different thread as the QML engine via context properties is dangerous to begin with. You cannot safely access properties or call methods of such objects from QML. I really recommend proxying the signals through a separate object that lives in the engine thread. Ulf Hermann added a comment - 30 Apr '19 10:02 PM The bad idea is not actually the connection. The fact that the connection behaves in the way described here is just the consequence of the fact that you're exposing an object from a different thread. The QML language has no concept of threads (besides WorkerScript, but that is a different beast), so exposing the C++ threading model to it via context properties is a bad idea. The engine does not magically provide thread safety for otherwise unsafe operations and it needs to inspect the objects given to it as context properties. Please make sure everything you expose to a particular engine lives in the same thread. Otherwise all bets are off anyway.

Hi, Good catch ! I just remembered that there was an issue in earlier versions where the deployment tool didn't properly copy all the needed plugins. It has been fixed in between.

@Ahti said in Inconsistency between model and view after removing a row from a table: JsonObject u_data; u_data.insert("id", model->record(index.row()).value(0).toInt()); u_data.insert("name", model->record(index.row()).value(1).toString()); if (role == Qt::DisplayRole) return u_data; That's inefficient. If you only support DisplayRole, then you can move that QJsonObject directly into that if statement. if (role == Qt::DisplayRole) { QJsonObject u_data; u_data.insert("id", model->record(index.row()).value(0).toInt()); u_data.insert("name", model->record(index.row()).value(1).toString()); return u_data; } Second, you should use the parent here, even if it is a flat list: beginRemoveRows(QModelIndex(), first, last); response = model->removeRow(first, QModelIndex()); beginRemoveRows(parent, first, last); response = model->removeRow(first, parent); But why you get this strange behavior when removing - I don't know. Perhaps it has something to do with the fact that you have two models here - UseModel is a list model and your model variable is a QSqlTableModel (which inherits from the same base class as list model). Perhaps these calls get duplicated, although it is unlikely. Try adding some qDebug() calls into removeRows(), or run it through a debugger, to see what is happening.