Fix documentation of QgsDateEdit and QgsTimeEdit classes (fixes #55758)

This commit is contained in:
Mathieu Pellerin 2024-01-24 16:07:11 +07:00 committed by Nyall Dawson
parent 63ec57237b
commit 51648deda1
3 changed files with 6 additions and 6 deletions

View File

@ -188,7 +188,7 @@ The :py:class:`QgsTimeEdit` class is a QTimeEdit widget with the capability of s
.. warning:: .. warning::
You should use the signal valueChanged of this subclass You should use the signal timeValueChanged of this subclass
rather than QDateTimeEdit.timeChanged. (If you consequently connect parent's rather than QDateTimeEdit.timeChanged. (If you consequently connect parent's
timeChanged signal and call :py:func:`~QgsDateTimeEdit.time` afterwards there is no guarantee that timeChanged signal and call :py:func:`~QgsDateTimeEdit.time` afterwards there is no guarantee that
NULL values will be correctly handled). NULL values will be correctly handled).
@ -243,7 +243,7 @@ The :py:class:`QgsDateEdit` class is a QDateEdit widget with the capability of s
.. warning:: .. warning::
You should use the signal valueChanged of this subclass You should use the signal dateValueChanged of this subclass
rather than QDateTimeEdit.dateChanged. (If you consequently connect parent's rather than QDateTimeEdit.dateChanged. (If you consequently connect parent's
dateChanged signal and call :py:func:`~QgsTimeEdit.date` afterwards there is no guarantee that dateChanged signal and call :py:func:`~QgsTimeEdit.date` afterwards there is no guarantee that
NULL values will be correctly handled). NULL values will be correctly handled).

View File

@ -188,7 +188,7 @@ The :py:class:`QgsTimeEdit` class is a QTimeEdit widget with the capability of s
.. warning:: .. warning::
You should use the signal valueChanged of this subclass You should use the signal timeValueChanged of this subclass
rather than QDateTimeEdit.timeChanged. (If you consequently connect parent's rather than QDateTimeEdit.timeChanged. (If you consequently connect parent's
timeChanged signal and call :py:func:`~QgsDateTimeEdit.time` afterwards there is no guarantee that timeChanged signal and call :py:func:`~QgsDateTimeEdit.time` afterwards there is no guarantee that
NULL values will be correctly handled). NULL values will be correctly handled).
@ -243,7 +243,7 @@ The :py:class:`QgsDateEdit` class is a QDateEdit widget with the capability of s
.. warning:: .. warning::
You should use the signal valueChanged of this subclass You should use the signal dateValueChanged of this subclass
rather than QDateTimeEdit.dateChanged. (If you consequently connect parent's rather than QDateTimeEdit.dateChanged. (If you consequently connect parent's
dateChanged signal and call :py:func:`~QgsTimeEdit.date` afterwards there is no guarantee that dateChanged signal and call :py:func:`~QgsTimeEdit.date` afterwards there is no guarantee that
NULL values will be correctly handled). NULL values will be correctly handled).

View File

@ -222,7 +222,7 @@ class GUI_EXPORT QgsDateTimeEdit : public QDateTimeEdit
* \ingroup gui * \ingroup gui
* \brief The QgsTimeEdit class is a QTimeEdit widget with the capability of setting/reading null date/times. * \brief The QgsTimeEdit class is a QTimeEdit widget with the capability of setting/reading null date/times.
* *
* \warning You should use the signal valueChanged of this subclass * \warning You should use the signal timeValueChanged of this subclass
* rather than QDateTimeEdit::timeChanged. (If you consequently connect parent's * rather than QDateTimeEdit::timeChanged. (If you consequently connect parent's
* timeChanged signal and call time() afterwards there is no guarantee that * timeChanged signal and call time() afterwards there is no guarantee that
* NULL values will be correctly handled). * NULL values will be correctly handled).
@ -268,7 +268,7 @@ class GUI_EXPORT QgsTimeEdit : public QgsDateTimeEdit
* \ingroup gui * \ingroup gui
* \brief The QgsDateEdit class is a QDateEdit widget with the capability of setting/reading null dates. * \brief The QgsDateEdit class is a QDateEdit widget with the capability of setting/reading null dates.
* *
* \warning You should use the signal valueChanged of this subclass * \warning You should use the signal dateValueChanged of this subclass
* rather than QDateTimeEdit::dateChanged. (If you consequently connect parent's * rather than QDateTimeEdit::dateChanged. (If you consequently connect parent's
* dateChanged signal and call date() afterwards there is no guarantee that * dateChanged signal and call date() afterwards there is no guarantee that
* NULL values will be correctly handled). * NULL values will be correctly handled).