Inconsistency QMessageBox.event() documentation Qt C++ and PySide6
-
After searching on internet, I found a code snipped to resize a simple
QMessageBoxvia an event as it is not officially supported or documented, but works:class ResizableMessageBox(QMessageBox): def __init__(self): QMessageBox.__init__(self) self.setSizeGripEnabled(True) def event(self, e): # Undocumented: The only way of resizing a QMessageBox is from an event result = QMessageBox.event(self, e) self.setMinimumSize(275, 125) self.setMaximumSize(500, 500) self.setSizePolicy(QSizePolicy.Expanding, QSizePolicy.Expanding) return resultWhen trying to understand the code and lookup function
event()in the PySide6 documentation, there is another inconsistency between C++ and PySide6 documentation:When the PySide6 documentation is generated from C++ code, why is the documentation incomplete and inconsistent? We already identified a very large number of PySide6 documentation issues.
-
Hi,
As already explained in other threads, the Python documentation is automatically generated from the C++ version. The process is not perfect but you will have better chance of improvement if you bring the issues you find on the Qt bug report system rather than on this user forum.
-
As already explained in other threads, the Python documentation is automatically generated from the C++ version.
This is just one example of unexpected inconsistency in documentation between C++ and PySide6, but found also other documentation issues like "forgot to update after a code change" and non-working examples. For us not minor details.
The process is not perfect but you will have better chance of improvement if you bring the issues you find on the Qt bug report system rather than on this user forum.
Another issue where we wasted lots of time creating test cases on non-working window move on Wayland was already requested by someone else to update documentation in September 2020 QTBUG-86780, but not resolved, no progress.
Issue reported, requested documentation update QTBUG-110119, closed, no update.It is simply impossible to create a test case and report all documentation issues individually without a follow-up. This is a commercial sold product where we expected a higher documentation quality.
-
As already explained in other threads, the Python documentation is automatically generated from the C++ version.
This is just one example of unexpected inconsistency in documentation between C++ and PySide6, but found also other documentation issues like "forgot to update after a code change" and non-working examples. For us not minor details.
The process is not perfect but you will have better chance of improvement if you bring the issues you find on the Qt bug report system rather than on this user forum.
Another issue where we wasted lots of time creating test cases on non-working window move on Wayland was already requested by someone else to update documentation in September 2020 QTBUG-86780, but not resolved, no progress.
Issue reported, requested documentation update QTBUG-110119, closed, no update.It is simply impossible to create a test case and report all documentation issues individually without a follow-up. This is a commercial sold product where we expected a higher documentation quality.
@Erriez said in Inconsistency QMessageBox.event() documentation Qt C++ and PySide6:
This is a commercial sold product where we expected a higher documentation quality.
If you have a commercial licence then you would be best raising your issues with TQtC rather than this user forum.
