@jdent said in How do I iterate across the columns of a QTableView so I can find the total width of the table?:

@Axel-Spoerl How can I get the vertical scrollbar of the QTableView?

Simply with verticalScrollBar()
cause QTableView inherits of QAbstractScrollArea ;)

@JonB you are correct!! it was select I was looking for!!

Thanks!

@jdent said in what determines the order of the pushbuttons in a dialog?:

QDialogButtonBox* buttonBox = new QDialogButtonBox; buttonBox->addButton(submitButton, QDialogButtonBox::AcceptRole); buttonBox->addButton(revertButton, QDialogButtonBox::ResetRole); buttonBox->addButton(closeButton, QDialogButtonBox::RejectRole);

The thing is, these roles make life easier, because they automatically accept or reject your dialog when being clicked. But like @JonB said, nobody forces you to use a QDialogButtonBox in your dialog. It's nice to have, but if you don't like the OS default order (on some OS "OK" is left and "Cancel" right and on some it's reversed), you can put them in a regular layout and manually handle the accept() / reject() states.

@jdent said in In a dialog, how can i determine which widget I want to make the active one upon load?:

is there no equivalent in Qt Designer?

See https://doc.qt.io/qt-6/designer-tab-order.html

I also needed this but there was no answer for it anywhere.
Here is my solution:

Dialog { id: loginDialog title: "Login" modal: true LoginDialog { id: loginPage anchors.fill: parent } footer: DialogButtonBox { id: buttons Button { id: okButton text: qsTr("Ok") DialogButtonBox.buttonRole: DialogButtonBox.InvalidRole Connections { target: okButton function onClicked() { if (CONDITION){ loginDialog.accept() } else { } } } } Button { id: cancelButton text: qsTr("Cancel") DialogButtonBox.buttonRole: DialogButtonBox.RejectRole } } }

So my answer is replace standard buttons and handle button clicks yourself.

Thanks for the ideas, I got it working like this now:

bool myWidget::event(QEvent* e) { if(e->type() == QEvent::Leave) { QPoint view_pos(x(), y()); QPoint view_pos_global = mapToGlobal(view_pos); QPoint mouse_global = QCursor::pos(); if(mouse_global.x() < view_pos_global.x() || mouse_global.x() > view_pos_global.x() + width()) { closeMenu(); } else if(mouse_global.y() < view_pos_global.y() || mouse_global.y() > view_pos_global.y() + height()) { closeMenu(); } } return QWidget::event(e); }

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

@jsulm
actually, it doesn't work at all, from my quick test I made.

I'm not entirely sure why...

need to check Qt classes for system settings and native look and feel,
and of adopting those changes for App.

Thanks,

No ideas? =(

Put the list widget in a layout. Here's more on layouts in Qt.

@KevinD said in Modal from a modal (Mac):
Hi,
Don't use these two:

box.setModal(true); box.setWindowFlags(box.windowFlags() | Qt::Popup);

You're calling QDialog::exec which is for modal-only dialogs, and Qt::Popup isn't for dialogs, leave the window flags be. If you prepare a MWE (the download-and-build type) I can test on Linux (I have no Mac, sorry). Also you might consider filing a bug report if everything else fails.

Kind regards.

@Rohith
no it's not.
You would have to implement your custom QDialog subclass.
Which shouldn't be much of an effort.

@p3c0 said:

Cast to QObject instead of QQuickItem.

That works. :)
Thanks.

I got it. Thank you for your help.

Hi @alex_malyu ,
Thank you for the detailed explanation. It makes more sense now.

Thank you!!

@aney
Yeah when meta compiler doesn't run, it all get a bit strange. :)

In first post , under it. to the right. is Topic Tools button. It can mark as solved.