X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/c398434d925aa9e2b190ce632fac1a79ffcbf043..efb091829601cf07df6c4316a3f6f705aaa81587:/interface/wx/datetime.h?ds=sidebyside diff --git a/interface/wx/datetime.h b/interface/wx/datetime.h index e8eb26d46d..7f01b64835 100644 --- a/interface/wx/datetime.h +++ b/interface/wx/datetime.h @@ -59,7 +59,7 @@ in 'free' format, i.e. allow them to be specified in any of possible ways. These functions will usually be used to parse the (interactive) user input which is not bound to be in any predefined format. As an example, - ParseDateTime() can parse the strings such as "tomorrow", "March first" and + ParseDate() can parse the strings such as "tomorrow", "March first" and even "next Sunday". Finally notice that each of the parsing functions is available in several @@ -821,7 +821,9 @@ public: This function tries as hard as it can to interpret the given string as date and time. Unlike ParseRfc822Date(), it will accept anything that may be accepted and will only reject strings which can not be parsed in - any way at all. + any way at all. Notice that the function will fail if either date or + time part is present but not both, use ParseDate() or ParseTime() to + parse strings containing just the date or time component. See ParseFormat() for the description of function parameters and return value. @@ -879,15 +881,15 @@ public: @see Format() */ bool ParseFormat(const wxString& date, - const wxString& format = wxDefaultDateTimeFormat, - const wxDateTime& dateDef = wxDefaultDateTime, + const wxString& format, + const wxDateTime& dateDef, wxString::const_iterator *end); /** @overload */ bool ParseFormat(const wxString& date, - const wxString& format = wxDefaultDateTimeFormat, + const wxString& format, wxString::const_iterator *end); /**