Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document surprising behaviour of wxDatePickerCtrl::GetRange() in wxMSW.

Browse Source 
wxMSW native control always has a built-in lower limit as MSW doesn't support
the dates before the year 1601 so wxDatePickerCtrl::GetRange() always returns
a valid range start, even if SetRange() hadn't been called to set it.

As this can be unexpected, document this behaviour clearly.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@67988 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2011-06-19 22:46:39 +00:00
parent 106f0d98f8
commit 58daa7b264
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
interface/wx/datectrl.h
View File

@@ -105,6 +105,11 @@ public:
range is set (or only one of the bounds is set), @a dt1 and/or @a dt2 range is set (or only one of the bounds is set), @a dt1 and/or @a dt2
are set to be invalid. are set to be invalid.
Notice that when using a native MSW implementation of this control the
lower range is always set, even if SetRange() hadn't been called
explicitly, as the native control only supports dates later than year
1601.
@param dt1 @param dt1
Pointer to the object which receives the lower range limit or Pointer to the object which receives the lower range limit or
becomes invalid if it is not set. May be @NULL if the caller is not becomes invalid if it is not set. May be @NULL if the caller is not