Qt for Python

Thanks for your information. I'm not getting any kind of resource too regarding the packaging.

@RemDup
The alternative way which should work is not to load the stacked widget initially. Show the main window and set off a 0 duration singleshot timer before entering the main event loop. In the slot, which will be run just after the main window (or whatever) is shown, create and load the other widgets.

@friedemannkleint The data that the model provides is not displayed in the tableview. When button is clicked, it should be emitting signal with the model that carries the data, so model=null is turned into model=actual data, then the data should be displayed on tableview. As you can see I've left part of the TableView block empty so someone could suggest the solution to this.

show your code. or record screen shot or video,

thanks it works closely but not perefect solution because few black pixels are still visible in edges.but its negligible

image.png

@Pl45m4, thanks. That works:

#!/usr/bin/env python3.13 main_content_dock.setFeatures( PyQt6.QtWidgets.QDockWidget.DockWidgetFeature.DockWidgetClosable | \ PyQt6.QtWidgets.QDockWidget.DockWidgetFeature.DockWidgetFloatable | \ PyQt6.QtWidgets.QDockWidget.DockWidgetFeature.DockWidgetMovable )

I'm stupid. It's because it was a 0-width HLine. Changed to VLine; worked.

I think I finally understand how .ui.qml, .qml and python backend should work together when working with QDS project.
Way I did this was to export component ID as property alias in QDS by clicking @ sign, as shown on screenshot:
Screenshot 2025-02-05 181658.png

Then this alias should be used in .qml files, such as App.qml in order to access the component in .ui.qml (This was the biggest confusion point for me). Then we can use signals and slots to connect components with backend as usual.

I created a minimal example and can be seen here in case anyone has same issue.
https://github.com/irakliskhirtladze/QML-Demo

@Mahdi_2020 You could simply use https://doc.qt.io/qt-6/resources.html

@andrei_cp
Maybe your resetting the pixmap to a new size in resizeEvent() in turn causes a new size event, and a bit bigger than before? That is the recursion.
In any case I imagine you want to use @friedemannkleint's suggestion, then you only need the label to resize, see if that helps.

QGuiApplication is a bit smaller...

You may try:

get visial rect of the item
QRect QTableWidget::visualItemRect(const QTableWidgetItem *item) const update it only
void QWidget::update(const QRect &rect)

check here out
https://www.qtcentre.org/threads/1032-repaint-a-cell-or-row-in-QTableWidget

Thank you very much !

Out of curiosity, have you tried building this with "pure" nuitka (not via pyside6-deploy)? I have completely given up on pyside6-deploy, but never really have any problems with nuitka for any platform.

I meant it's achieved internally so you don't have to do anything special unless you are doing your own rendering.
QScreen would be of interest.

@Pl45m4

Thanks for your explanation! I'll keep you posted if I find out something new on this topic.