Qt for Python (PySide/Shiboken) — messages on 5 July 2022

5 July 2022

Hello Qt for Python folks! Say for QErrorMessage is there really no official way to tell if the user ticked the checkbox or not? https://doc.qt.io/qtforpython/PySide6/QtWidgets/QErrorMessage.html

08:12

Or even set it! One HAS to carry an instance around to keep track of the checked state? Or you actually look under the .children() of the thing and get/set the checkbox 0: <PySide2.QtWidgets.QLabel(0x229ec6bd2b0) at 0x00000229800B0C40> 1: <PySide2.QtWidgets.QTextEdit(0x229ec6bcdb0) at 0x00000229800B0440> 2: <PySide2.QtWidgets.QCheckBox(0x229ec6bd8b0) at 0x000002298011DD00> 3: <PySide2.QtWidgets.QPushButton(0x229ec6bcff0) at 0x000002298011DA80> 4: <PySide2.QtWidgets.QGridLayout(0x229ef45e820) at 0x000002298011D940>

08:15

Freya

I suppose you could use findChildren to find it, but that'd be quite a hack, yep

08:16

what's your goal? It sounds like you want to do something custom with the checkbox, so why use QErrorMessage at all then?

08:17

ëRiC

yeah that seems bizzare and barely usable. More likeley one implements a version on its own

08:17

Freya

it seems to do exactly what it's intended to do, yet you want it to do something entirely different?

08:18

ëRiC

I was going through the standarddialogs example.

08:19

Freyait seems to do exactly what it's intended to do, yet you want it to do something entirely different?

I don't mean to say that it's not working. It is! But: It's presenting key functionality that one has no obvious access to.

08:22

Freya

But the whole point of QErrorDialog is that it handles that thing itself, no?

08:23

ëRiC

But wouldn't you want to have access to the users decision to show that message again?

08:24

I mean maybe you could pickle the dialog instance somehow and save the whole thing to disk to make it persistant?

08:27

that's how it currently works. You'd need to keep THE one instance alive forever to make this work persistently. I'd rather store a single bit for that somewhere somehow.

08:29

Freya

But then access to the checkbox alone won't help you either, unless you want to reimplement the whole "messages already shown" logic, at which point you probably just should use your own thing.

08:30

ëRiC

Yeah I just tried to set the checkbox before showMessage that won't help. The Diaolg pops up with the checkbox unticked 😃

08:42

The simpledialogsexample seems to suggests that QErrorMessage is derrived from QMessageBox but the .checkBox() method is not even there although it would have been obvious.

08:44

Semih Şevik

Ссылка
click to show

Hi, I tested the freezing problem of qt on the touch screen in different versions of PySide. I shared the test results (videos) in the link. As you can see from the videos, PySide2-5.13.2 version does not have freezing problem. But in the latest versions of PySide2 and PySide6 the touch screen freezes. Thank you. PySide2-5.13.2 = https://www.veed.io/view/5210b05a-4d35-4788-9017-82dca381b9d2 PySide2-5.15.2.1 & PySide6-6.3.1 = https://www.veed.io/view/645f04ec-b389-4a43-97b2-a97eabf63685

15:53

Keith Kyzivat

Semih ŞevikHi, I tested the freezing problem of qt on the touch screen in different versions of PySide. I shared the test results (videos) in the link. As you can see from the videos, PySide2-5.13.2 version does not have freezing problem. But in the latest versions of PySide2 and PySide6 the touch screen free

Can you share the sources of your test application? If it's simple enough, I can try translating it to c++ to verify it's a Qt issue and not a PySide one. (Presuming it's not in your application logic)

16:28

And actually, why don't you report this as a bug at https://bugreports.qt.io/ , attach your test application (fine if it's python)

16:29

id 197506226

We tried its not pyside bug

16:54

Reported 👍

16:54

A snapshot of an open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.