ëRiCtext not yet in the index
So what the solution should be? How should I add the stub to my project keeping the rest of PySide6 stubs unchanged?
Considering the .pyi files are generated automatically in the project, I'd recommend trying to upstream these changes/improvements. Modifying the .pyi by hands is not a good idea because you can get them lost by updates.
There is also a project called PySide6-Stubs, where the person is editing them manually, and upstreaming the reports, so we can fix them, which is also a good approach.
Cristián 🥑contributing fixes to the stubs generation infrastructure we have is not simple, so that's why even with reporting these details, we can make them better :)
That's the underestimation of the year. Without proper docs on the XML files, it's next to impossible to guess what to do there. And the docs @take5v might be interested in are at https://doc.qt.io/qtforpython-6/shiboken6/typesystem.html. However, I have no idea how to reach them browsing from https://doc.qt.io/qtforpython-6/.
From https://doc.qt.io/qtforpython-6/ you check the grid-menu and click on 'Shiboken' then you click on the grid-menu 'type system'
There are many different corner cases wrt modifying the stubs.
1. If only the return type is incorrect, that's the easiest because you can rely on the pyi-type like qVersion https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6/QtCore/typesystem_core_common.xml#n44
2. A similar approach for arguments can be follow like in the case 1. but only if there is a proper conversion mechanism within the method (might require injecting code to fix it) like "qUncompres(...)" https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6/QtCore/typesystem_core_common.xml#n60
3. the most difficult change will be one that imply changing how the generation works. For exaple, there was a report long time ago about missing information for some class attributes that needed to handle class attributes differently: https://codereview.qt-project.org/c/pyside/pyside-setup/+/543006 (which had a flaw as well)
I'm certain I'm forgetting a few more cases, but those are from the top of my head.
Whenever I have time (and oher devs as well) we do read the chat and try to help, but I'd love to hear any other issues of missing documentation on topics, we can take some time and write things down!
So when we say, please fill a suggestion or bug report in jira, is not to dismiss you, but to remember and do it :)
QML docs are next to empty. 🙁
Some links are missing: https://doc.qt.io/qtforpython-6/overviews/qtquick-bestpractices.html#id10
Some code is missing: https://doc.qt.io/qtforpython-6/overviews/qtquick-how-tos.html#call-a-c-function-from-qml-when-a-button-is-clicked
Some sections are wrecked: https://doc.qt.io/qtforpython-6/overviews/qtquick-visualcanvas-scenegraph.html#driving-animations
I can't report all the errors there are in the docs. They're just everywhere. Only the docs on QML classes look fine.
Anton YablokovQML docs are next to empty. 🙁
Some links are missing: https://doc.qt.io/qtforpython-6/overviews/qtquick-bestpractices.html#id10
Some code is missing: https://doc.qt.io/qtforpython-6/overviews/qtquick-how-tos.html#call-a-c-function-from-qml-when-a-button-is-clicked
Some sections are wrecked: https://
The problem I see with those links is that they are the auto-translated from the Qt/C++ documentations.
Long time ago we had a similar discussion that between only having a few docs that we wrote by hand, and having some half-backed translated ones from Qt/C++, we opted for the last.
Addressing that type of fixes is very difficult because we might need to add corner cases in the doc translator.
This open a new question: does it make sense to replicate the documentation of something non-python specific in the qt for python docs?
That precisely contains some CMake things that make no sense in the Python world, that's why we decided to have Tutorials and examples on that topic:
https://doc.qt.io/qtforpython-6/tutorials/index.html#quick-qml-basic-tutorials
As you can see, your links only comes from the fact that you are probably using the "search" functionality, instead of using the grid categories from the main page: https://doc.qt.io/qtforpython-6/index.html which is what we have manually crafted.
If your answer is "But I want to have a Qt Quick best practices page with python code" that needs to be extrapolated of ALL the overview pages, and other things that Qt/C++ has.
Sadly, we are a small team of 5 people (2 full times on qt for python, and 3 with half-time working on the project), that really cannot be done with the current configuration,
but it's a super simple way of start contributing to the project, because finding the most important overview pages, manually updating them, and avoid doing the auto-generation might be the only way.
Plan B is for you (and everyone else) to report which overviews pages needs to be manually updated, so we can create new tutorials on that topic.
id 24766519Guys, thank you for PySide 6.8.3 🎉🥳 There are 0 problems in my small project (win, linux) ❤️
GIF
whew-goldblum.mp4 · 49 KB · click to show
whew-goldblum.mp4 · 49 KB · click to show
Hey experts!
quick question:
I'm building a GUI with custom widgets and mapping them using QDataWidgetMapper. The data in my QAbstractTableModel includes different types (bool, int, float), and each widget is designed to handle a specific type, like:
bool → LED
int → textbox with multicolor LED
float → textbox with gauge
I want to design these widgets so they require minimal, or no custom code, to work with the mapper, ideally just:
mapper->addMapping(widget, section, THIS_PROPERTY)
What should I name the getter/setter methods (at maximum for THIS_PROPERTY) in my custom widgets to make this work seamlessly?
Any useful docs or examples on this would be much appreciated!
🙏
in most cases it should work, because it will contain only bug fixes, but we do have cases in the past that due to some missing symbols there was a breakage so it was not working.
You can judge if it's worth it by the changes: https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.8.3 (those are the highlights, a few minor ones were also around).
If you find something, let us know so we can keep track of that for the next bug-fix releases of 6.9.x
Also keep in mind 6.8.3 is the last release of the 6.8 series, but the source code of 6.8.4 will be around in a year after that release (which is still not planned)
Ссылка
click to show
click to show
Hello, the blog post about PyCRDT and PySide is published: https://david-brochart.medium.com/making-qt-collaborative-using-crdts-94c470703253
Hello!
I wanted to create my own custom panel design instead of the system one, but the window cannot be dragged or positioned programmatically on Linux. I compiled it with Nuitka, but it still won't move—it always appears in the top-left corner. On Windows, everything works fine. I'm using the latest version of PySide6.
If I'm not mistaken, Telegram Desktop is written in Qt, and their custom panel works perfectly on Linux.
Ссылка
click to show
click to show
Wayland's authors present it as a feature. They deliberately return QPoint(0, 0) for the global window position and ignore attempts to move it. They say, it's for security and greater flexibility. See https://doc.qt.io/qt-6/application-windows.html#wayland-peculiarities or google “wayland move window”.
Anton YablokovAnd no, the Telegram app doesn't move from the center of the screen on its own. Not for me, not in KDE Neon. That's why I'd rather put my PC to sleep than shut it down, so I don't place all the apps manually every day.
Does Wayland have a means of writing a compositor extension that can manipulate window positions? That might be a workaround...
There are some hints on it. But I haven't understood them. For example, I'm too lazy to figure out where to place the XML data as written at https://wayland-book.com/xdg-shell-in-depth/interactive.html