don't check whether the window is shown and enabled in AcceptsFocus() itself

as it makes overriding it in derived classes problematic; provide a separate
non virtual CanAcceptFocus() method checking whether the window accepts focus
and if it can accept it now and use it instead of AcceptsFocus(); documented
AcceptsFocus() and AcceptsFocusFromKeyboard()


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@45055 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2007-03-25 22:36:24 +00:00
parent 4542739ccb
commit ad02525dad
14 changed files with 52 additions and 17 deletions

View File

@@ -171,6 +171,29 @@ can delete a window only when it is safe to do so, in idle time.
\helpref{wxCloseEvent}{wxcloseevent}
\membersection{wxWindow::AcceptsFocus}\label{wxwindowacceptsfocus}
\constfunc{bool}{AcceptsFocus}{\void}
This method may be overridden in the derived classes to return \false to
indicate that this control doesn't accept input at all (i.e. behaves like e.g.
\helpref{wxStaticText}{wxstatictext}) and so doesn't need focus.
\wxheading{See also}
\helpref{AcceptsFocusFromKeyboard}{wxwindowacceptsfocusfromkeyboard}
\membersection{wxWindow::AcceptsFocusFromKeyboard}\label{wxwindowacceptsfocusfromkeyboard}
\constfunc{bool}{AcceptsFocusFromKeyboard}{\void}
This method may be overridden in the derived classes to return \false to
indicate that while this control can, in principle, have focus if the user
clicks it with the mouse, it shouldn't be included in the TAB traversal chain
when using the keyboard.
\membersection{wxWindow::AddChild}\label{wxwindowaddchild}
\func{virtual void}{AddChild}{\param{wxWindow* }{child}}