Qt for Python

It's a question of object lifetime or rather garbage collection. I have got hit by this one some years ago.

Eventually found this. Since the start and end edge code are very similar, I develop the start-side code, and get all the pointers connected up properly first edge - port - node can get a little tricksy! And then I do the end-side, copying and pasting, and change all (<-- hint) the start variables to the matching end variables. Except I missed one. Now found. All good.

@rida_zouga Sorry, yes, I forgot you said Python. I just search/post links from C++ reference pages. https://doc.qt.io/qt-6/qtwebengine-changes-qt6.html#qwebenginepage QWebEnginePage Has been moved to Core, and API that worked on QWebEngineView or QPrinter has been moved, and can now be accessed only from QWebEngineView. See Changed API.

@JonB Thanks for the link! There's border-radius, which makes the plain "StyledPanel" style possible but the website only mentions a shadow for "PaletteRole". Does this mean that you can't achieve the "raised" or "sunken" styles purely using QSS?

Hi, From old memories, you need to create the initial context first and then share it with the others and don't forget the creat calls. This Reddit thread might be what you are looking for.

@JohnL53 hi and welcome to devnet, Which variant of Debian are you running ? Did you consider using the online installer to get Qt ?

sudo apt install pyqt6-dev-tools solved it for me on Ubuntu.

The bindings for QtOpcUa, QtMqtt and QtCoap are provided for commercial license owners as part of the commercial offering. So, the contribution can unfortunately not be accepted.

seems like an issue with Nuitka. I created a bug here - https://qt-project.atlassian.net/browse/PYSIDE-3312 in Qt for Python, but this actually would need a bug to be filed in Nuitka which i can do soon.

See PYSIDE-3286 for reference.

Hi and welcome to devnet, macOS has certain rules (as other OS do as well) to have a consistent user experience and Qt helps to put things into the right place automatically. For example, the settings are under Preferences in the application's name menu. User don't have to hunt down for these kind of things. On macOS the default QMainWindow menu bar is indeed at the top of the screen which is normal and expected. Taking a look at your code and the picture you posted, I would suggest to redesign things a bit. For example, having the dark/light theme switch under Help is rather unexpected.

Hi, Did you check the Eratosthenes example ? It used the QtAsyncio.run method to start the event loop and asyncio integration. When reading the example, check that you have the asyncio implementation shown as there are two different implementations shown. Hope it helps

This eventually turned out to be an unneeded call in the parent.paint, which got very confused when the item had been deleted. Keeping everything clean and as simple as possible helps.

Hi and welcome to devnet, You should open a feature request on the bug report system. That will be the right place to discuss this kind o things. This forum is more user oriented.

Now I'm working on drawing a vertices cloud for a model imported from polygon, and I was puzzled about this issue as well. I've tried changing point size in .vert file, but no effect actually. Anyway, shader files in Qt are seriously hard to compile successfully.

@pasmon90 said in Drawing LaTeX image in pyside6 using TextObject: I need python equal or greater than .12 for gemini api feature So i cannot use pyqt6 as it does not get install. I know nothing about your situation. But if you are saying that PyQt6 would work, or is at least worth trying to compare against PySide behaviour, have you tried running PyQt6 with whatever 3.12/3.13 version of Python, regardless of whether PyQt6 is supplied with an older version of Python?

Thank you for the warm welcome! I use this QT-version: Name: PySide6 Version: 6.7.2 Summary: Python bindings for the Qt cross-platform application and UI framework Home-page: Author: Author-email: Qt for Python Team <pyside@qt-project.org> License: LGPL Location: /home/pi/.local/lib/python3.11/site-packages Requires: PySide6-Addons, PySide6-Essentials, shiboken6 Required-by:

@J.Hilk said in PyQt: I know I don't like that as well, but at least it reduced the confusion between Qt and QtCreator versions by an order of magnitude in posts here on the platform Not sure what you mean. I started at Qt5 a few years ago. We are now at Qt6. Meanwhile Creator went from something like major version 4 to major version 19, or thereabouts. I can't really see much has even changed in it (at least for my usage; and for me it has about the same number of major bugs/annoyances as it did at version 4, no improvements in lots of those). Certainly not enough to justify ~15 major version increments. If this were any other product than Qt, which I do love, I would not touch it with a bargepole if it need to undergo so many, frequent major version numbers.

Thank you ! :-)