From 7d4cb1eff58fc318e095f14bab340c387b856769 Mon Sep 17 00:00:00 2001 From: Vadim Zeitlin Date: Wed, 15 Sep 2010 22:10:26 +0000 Subject: [PATCH] Document limitations of the generic wxTextEntry hints. Calling methods other than SetValue() or ChangeValue() doesn't update the display correctly currently, see #12475. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@65553 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- interface/wx/textentry.h | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/interface/wx/textentry.h b/interface/wx/textentry.h index a7110f592a..74d7a88dc8 100644 --- a/interface/wx/textentry.h +++ b/interface/wx/textentry.h @@ -375,6 +375,16 @@ public: Notice that hints are known as cue banners under MSW or placeholder strings under OS X. + @remarks For the platforms without native hints support (and currently + only the MSW port does have it and even there it is only used under + Windows Vista and later only), the implementation has several known + limitations. Notably, the hint display will not be properly updated + if you change wxTextEntry contents programmatically when the hint + is displayed using methods other than SetValue() or ChangeValue() + or others which use them internally (e.g. Clear()). In other words, + currently you should avoid calling methods such as WriteText() or + Replace() when using hints and the text control is empty. + @since 2.9.0 */ virtual void SetHint(const wxString& hint);