mirror of
https://github.com/qgis/QGIS.git
synced 2025-10-16 00:05:45 -04:00
Fix documentation of QgsDateEdit and QgsTimeEdit classes (fixes #55758)
This commit is contained in:
parent
63ec57237b
commit
51648deda1
@ -188,7 +188,7 @@ The :py:class:`QgsTimeEdit` class is a QTimeEdit widget with the capability of s
|
||||
|
||||
.. 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
|
||||
timeChanged signal and call :py:func:`~QgsDateTimeEdit.time` afterwards there is no guarantee that
|
||||
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::
|
||||
|
||||
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
|
||||
dateChanged signal and call :py:func:`~QgsTimeEdit.date` afterwards there is no guarantee that
|
||||
NULL values will be correctly handled).
|
||||
|
@ -188,7 +188,7 @@ The :py:class:`QgsTimeEdit` class is a QTimeEdit widget with the capability of s
|
||||
|
||||
.. 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
|
||||
timeChanged signal and call :py:func:`~QgsDateTimeEdit.time` afterwards there is no guarantee that
|
||||
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::
|
||||
|
||||
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
|
||||
dateChanged signal and call :py:func:`~QgsTimeEdit.date` afterwards there is no guarantee that
|
||||
NULL values will be correctly handled).
|
||||
|
@ -222,7 +222,7 @@ class GUI_EXPORT QgsDateTimeEdit : public QDateTimeEdit
|
||||
* \ingroup gui
|
||||
* \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
|
||||
* timeChanged signal and call time() afterwards there is no guarantee that
|
||||
* NULL values will be correctly handled).
|
||||
@ -268,7 +268,7 @@ class GUI_EXPORT QgsTimeEdit : public QgsDateTimeEdit
|
||||
* \ingroup gui
|
||||
* \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
|
||||
* dateChanged signal and call date() afterwards there is no guarantee that
|
||||
* NULL values will be correctly handled).
|
||||
|
Loading…
x
Reference in New Issue
Block a user