Hi @SGaist Thank You For Your Answer!
And Sorry For My Question is Not Clean Because My English Is Not Good! :)

your community is so kind

Reported as QTBUG-108047

@jsulm Thank you. I gotta take a look at it.

@jsulm Yes, thank you, two clicks and now it works great, was looking for such a long time for this..

@LT-K101
You write a dialog to ask the user whether they want to print and if they say yes you call printToLocalPrinter() or printToDisk() or similar. I'm not writing that for you, it's a dialog, I have no idea what your issue is. You also already have a printReport() shown earlier which does a getSaveFileName() and calls printToDisk(filename), so I don't know what your problem is.

@CristianMaureira huh, I don't know what happened here, but it was actually installed from pip and not from the system package manager.

See TimerType for some insights. Basically coarse timers are adjusted slightly to fire multiple timers at the same time if possible, reducing wakeups and thus saving power. Precise timers don't do that.

@DerReisende said in How to scale a image by QImageReader:

setAllocationLimit

Thanks， it works.

@mister-pyside
Hello and welcome.

I'm afraid I'm not sure what you asking/saying, but: do you mean at design-time you have separate pages and you have not set up for/created any pages in the QWizard? You should just be able to call QWizard::addpage() or QWizard::setPage() to add existing widgets as pages at run-time?

I think you are saying this in

Now the problem comes in: I am not able to assemble the inheriting QWizardPages in the inheriting QWizard, the QWizard just never gets started.

Since I wish to define the order of the QWizardPages myself, I use setPage() to set instances of my inheriting QWizardPage classes with their position in the inheriting QWizard class.

In which case show your runtime code, as all of this should work, and I don't know what you mean by "the QWizard just never gets started".

The solution is https://doc.qt.io/qt-6/qtableview.html#resizeRowsToContents

@bashtian said in Speed up UI refresh:

Maybe there is a way to load all the forms in parallels using threads or something?

Seems to be not really an option to use threads here. Anything UI-related can only be done in the main thread.

If all data has the same layout a QTableView could make sense here. Your table columns would be name, width, height, x, y, header_text_color and header_background_color. The QTableView needs a model which would be your own class derived from QAbstractItemModel. The advantage ov QTableView is that it only instantiates the widgets that are currently visible (in contrast to QTableWidget where you would add all widgets after parsing the yaml -> same problem as before).

If you insist on not using QTableView because you want to keep your layout, you should still copy the approach of QTableView. I guess you already have a QScrollArea for all your entries. You get better performance if you only create the widgets for the entries that are currently visible. (On second thought: maybe get rid of QScrollArea and use just the QScrollBar directly.) The scrollbar will tell you what the first entry is to display. You should be able to compute how many entries can be displayed inside the surrounding widget. Just create the necessary widgets and display those (kind of do your own static layouting).

Hi and welcome to devnet,

Did you already check the Simple Widget Mapper Example ?

It's a pretty good starting point.

Hi,

From the look of your widgets:

Text Boolean Number

To find which type for which widget, look at the user property of the widget. Otherwise you can configure which property the mapper shall use with the widget assigned.

QDataWidgetMapper maps one column with one widget so a button group would not make sense.

@probiner
Wrong, you will be able to use QSortFilterProxyModel against QStandardItemModel. What I pointed out was: QSortFilterProxyModel::setSourceModel(QAbstractItemModel *sourceModel) means that it can act as a proxy on any QAbstractItemModel. The docs tell you that QStandardItemModel inherits QAbstractItemModel. Therefore QSFPM can accept QSIM as its source model. And if it some point you derive your own model class from QAbstractItemModel the proxy will work against that for the same reason. This is what inheritance means in C++ and in Python.

Hi and welcome to devnet,

You can mix widgets into QML however you can use QQuickWidget to integrate Qt Quick GUIs into a widget application.

KDAB has created the Declarative Widget module to allow putting widgets into QML however I don't think there are python bindings for it.

Hi and welcome to devnet,

What happens if you run your application without qasync ?
Shouldn't you use loop.exec() ?

@GaryN
Be aware as you progress that this "move globals/enumerates into specific class/namespace" has basically happened everywhere in Qt6/PyQt6. Old code/examples are going to be wrong for loads of these, not just the alignment flag ones...!

@JonB Thanks a lot it worked!!!

I also have this problem, my environments are
1, OS: ubuntu20.04
2, conda: 4.13
3, PyQt5: 5.15.2
4, local Qt5: 5.15.6
5, opencv- python 4.5.x

It really takes several days to find a solution, @jeremy_k gave almost the solution. I use PyQt5 + OpenCV-python on conda virtual environment,
summarize the solutions :

1, delete cv2/libqxcb.so, it works for pyqt5 which has its own version of Qt, but opencn-python doesn't work for other application which isn't relevant to PyQt5

2, if pyside2 is installed, pyside2 has its owen version of Qt, so add below code at the beginning of python program

``` import PySide2 dirname = os.path.dirname(PySide2.__file__) plugin_path = os.path.join(dirname, 'plugins', 'platforms') os.environ['QT_QPA_PLATFORM_PLUGIN_PATH'] = plugin_path ```

this solution works, at expense of intalling pyside2 which is 400M+

3, PyQt5 has its own version of Qt,similiar to above, add below code at the beginning of python program

``` import PyQt5 dirname = os.path.dirname(PyQt5.__file__) plugin_path = os.path.join(dirname, 'Qt5','plugins', 'platforms') os.environ['QT_QPA_PLATFORM_PLUGIN_PATH'] = plugin_path this soltuion is fine,

Hi @JonB, thank your very much for your tests and inputs!
I mostly agree with everything you wrote. A couple more commens:

about this part

Maybe as a workaround you do not need to use Qt's QLocale for this? The rest of your code is Python-only, not Qt. Python has its own locale-strings handling, perhaps you could use that instead of the broken QLocale one?

Yes, I thought about it and indeed Python is able to do the job. Maybe I didn't dig deep enough but I found a way how to do it only via switching of locale back and forth. And Python manuals are strongly against it - they warn of various side effects that happens with locale switching and advise not to do it this way.

About workaround itself - it appears that for my needs everything is related with QLocale().decimalPoint() and QLocale().groupSeparator() so I think I'll be able to make proper replacements with my own Python code. I'll try to report this as a bug, but a bit later, when I'll have some spare time for it.