Qt for Python

The QPdfView widget text selection functionality is currently not completely implemented or has bugs, see for example https://bugreports.qt.io/browse/QTBUG-131443 .

You have a mix of PySide6 and PyQt6 here, what are you using, really?

I have used CodeMorpher a while back.

Thanks for the advice!! In case anyone wants to look at the ticket here it is: https://bugreports.qt.io/browse/QTBUG-139410

Excellent ! Then please mark the thread as solved using the "Topic Tools" button or the three dotted menu beside the answer you deem correct so other forum users may know a solution has been found :-)

@JKSH, thank you. post/744511 explains well how to code for this.

@Alhazred, they appear to all be Python now: [image: 15ef3bc4-ae26-458e-aef6-1f2d7d87fb4f.png]

@SGaist Hi, ok, thank you. If I do not report back, assume it worked like the non-commercial version.

@JonB Thanks for the suggestion. That kinda seems to work and the checkbox is no longer overlapped with the text, but the resizeColumnstoContents() still seems to be taking into account of only the size of the text and I'm not sure how to recalculate that as I dont see sectionSizeHint() or sectionSize() being called. I added this right before the super() call: if logicalIndex in self.checkboxes: rect.adjust(23, 0, 0, 0) [image: 28b099a9-8165-4bc2-9547-74044338bd8e.png]

It shows both monitors in Windows Display settings as well.

This is exactly what I was looking for recently, and sadly I couldn’t find one either. However, you can integrate your own widgets into Qt Designer by creating a custom widget plugin. Qt Creator even provides a boilerplate project template for this in C++ (I’m not sure yet on the PySide process), so it’s pretty easy to get started. Once built, your plugin will appear in Designer just like the default widgets. [image: 51bfaceb-03f2-4bc9-9415-9cc26ffb1cfb.png] I recently built one myself in C++ for another project using Fluent UI–style widgets. The repo’s here if you’d like to take a look: https://github.com/alviansm/QtFluentWidgetPlugin. [image: 15bcfce7-11db-4258-80bd-c12df69115fa.png]

@Josef-Michael-Laub You should just put a layout (e.g. QHBoxLayout or QVBoxLayout) on the QDialog (via setLayout()) and then add the QChartView onto that (via addWidget()), just like adding any QWidget onto any other QWidget. About the only addChild() I know of is in QTreeWidgetItem and that is nothing to do with your situation.

@SGaist said in pyqt5，Curve rendering error: Hi and welcome to devnet, Without any code to reproduce that, there's only a very slight chance someone can guess what might be going on. Please provide a minimal script that shows this issue. Thanks, I have found the solution：When using a new brush, the program needs to set setBrush(Qt.NoBrush)

What Python version are you using? Starting from 3.11, tomllib is used which should be able to handle it. For older versions, a manual parser is used, which may fail.

@friedemannkleint This did not work either, although I wasn't getting any errors as such

Yes, I also encountered that. Sadly, that's exactly what it means: PySide's asyncio event loop does not implement getaddrinfo: https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6/QtAsyncio/events.py#n552 In fact, none or almost none of the IO-related methods are implemented. Documentation also says that directly at https://doc.qt.io/qtforpython-6/PySide6/QtAsyncio/index.html: We consider that this API consists of two levels: Fundamental infrastructure for event loops and asynchronous operations, including futures, tasks, handles, executors, and event loop management functions (see below). A user-facing API for use in applications, including transports and protocols, network connections, servers, sockets, signals, subprocesses. QtAsyncio currently covers the first level.: One solution is to use trio in guest mode, like in this example: https://doc.qt.io/qtforpython-6/examples/example_async_minimal.html. Except it will not help you, because LangChain does not support trio. There are a few libraries that implement a similar capability for asyncio, but none of them seem particularly mature.

Ok, I better understand your issue. I am currently wondering whether QtAsyncio should have followed more closely that design.

It seems to me that the @QMLElement would be necessary to introduce new elements to QML. My problem is the communication between the ui.qml (only geometry, rectangles, buttons) from Qt Design Studio and the .qml (events, signals for buttons, radiobuttons,...) e.g. from Qt Creator. I don't know how to refer/connect the objects in ui.qml to/with the associated events in .qml, I guess. Button with id=button1 in ui.qml and on the other hand button1.onClicked in .qml, how can I address to button1 from ui.qml to qml?

The problem had been solved,my windows version does not match minimal requirements