Qt for Python

@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: [image: 9db015ee-13e0-4bbe-9cc7-0999fc6bfab1.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.

@JonB I'm actually using the latest PyCharm version. This only happens with the latest PyQt6 version 6.8.0, and works fine with PyQt6 6.7.1, so it's probably an issue with the latest PyQt6 version, not the IDE.

Well it's nice to know it's in good hands :)

I've finally found the solution, it was indeed the eventloop. The process will only be destroyed after the next loop. match_manager.py # Mettre à jour les variables dans le fichier Excel ExcelToPdfWorker.update_variables(excel_path, variables) # Connecter le signal avant de décharger le PDF match_widget.editor.pdf_unloaded.connect( lambda: self._convert_after_unload(match_widget, excel_path) ) match_widget.editor.unload_pdf() def _convert_after_unload(self, match_widget, excel_path): """Appelé quand le PDF est vraiment déchargé.""" self.excel_worker.excel_path = excel_path self.excel_worker.convert() # Une fois la conversion terminée, on peut recharger le PDF match_widget.editor.load_new_pdf(match_widget.pdf_path) editor.py def unload_pdf(self): """Ferme le PDF actuel et nettoie les références.""" # Détacher la vue du document actuel self.pdfView.setDocument(None) # Fermer et supprimer l'ancien document if self.pdfDocument: old_document = self.pdfDocument # Créer un nouveau document vide avant de détruire l'ancien self.pdfDocument = QPdfDocument(self) # Connecter le signal destroyed à l'émission de notre signal old_document.destroyed.connect(self.pdf_unloaded.emit) old_document.close() old_document.deleteLater() def load_new_pdf(self, pdf_path): """Charge un nouveau fichier PDF.""" # Charger le nouveau PDF self.pdfDocument.load(pdf_path) self.pdfView.setDocument(self.pdfDocument) print(f"Nouveau PDF chargé: {pdf_path}") return True I'm well aware that my code sucks. Here's the solution. As deleteLater() really destroy the PdfDocument and unload it, you have to wait until the end of a complete cycle and return to app.exec(). Then I put in a signal that will convert the file once the reference has been destroyed, since we know that this frees access You should know that I think this is the only method without making temporary files

Thank you for all the help guys! I just needed to search about "Adding new widgets dynamically", but I didn't know it was called like this. This is the final result: def addRow(self, r): self.newLayoutRow = QtWidgets.QHBoxLayout() self.newLayoutRow.setObjectName("newLayoutRow_" + str(r)) self.newTimeEdit = QtWidgets.QTimeEdit(self.sorting0) self.newTimeEdit.setObjectName("newTimeEdit_" + str(r)) self.mainGrid.addWidget(self.newTimeEdit, r, 0, 1, 1) self.QComboBox1 = QtWidgets.QComboBox(self.sorting0) self.QComboBox1.setObjectName("QComboBox1_" + str(r)) self.newLayoutRow.addWidget(self.QComboBox1) self.QComboBox2 = QtWidgets.QComboBox(self.sorting0) self.QComboBox2.setObjectName("QComboBox2_" + str(r)) self.newLayoutRow.addWidget(self.QComboBox2) self.QSpinBox = QtWidgets.QSpinBox(self.sorting0) self.QSpinBox.setObjectName("QSpinBox_" + str(r)) self.newLayoutRow.addWidget(self.QSpinBox) self.mainGrid.addLayout(self.newLayoutRow, r, 1, 1, 1) Now just need to add some for loops and it's good to go

@Dwarrel Well it kind of is the solution, in that you want to compare the two both running with the same PYTHONPATH.