X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/4d0f3cd6ac9b38521b35f21cb94ef7d72aa34b9e..e0976f6db35b304f16519437c9d9e2450a373783:/docs/latex/wx/notifevt.tex diff --git a/docs/latex/wx/notifevt.tex b/docs/latex/wx/notifevt.tex index bdd5ac9e01..2fdce6f8e4 100644 --- a/docs/latex/wx/notifevt.tex +++ b/docs/latex/wx/notifevt.tex @@ -11,13 +11,16 @@ change if it wants to prevent it from happening. \helpref{wxCommandEvent}{wxcommandevent}\\ \helpref{wxEvent}{wxevent}\\ -\helpref{wxEvtHandler}{wxevthandler}\\ \helpref{wxObject}{wxobject} \wxheading{Include files} +\wxheading{Library} + +\helpref{wxCore}{librarieslist} + \wxheading{Event table macros} None @@ -32,14 +35,23 @@ None \func{}{wxNotifyEvent}{\param{wxEventType}{ eventType = wxEVT\_NULL}, \param{int}{ id = 0}} -Constructor (used internally by wxWindows only). +Constructor (used internally by wxWidgets only). + +\membersection{wxNotifyEvent::Allow}\label{wxnotifyeventallow} + +\func{void}{Allow}{\void} + +This is the opposite of \helpref{Veto()}{wxnotifyeventveto}: it explicitly +allows the event to be processed. For most events it is not necessary to call +this method as the events are allowed anyhow but some are forbidden by default +(this will be mentioned in the corresponding event description). \membersection{wxNotifyEvent::IsAllowed}\label{wxnotifyeventisallowed} \constfunc{bool}{IsAllowed}{\void} -Returns TRUE if the change is allowed (\helpref{Veto()}{wxnotifyeventveto} -hasn't been called) or FALSE otherwise (if it was). +Returns true if the change is allowed (\helpref{Veto()}{wxnotifyeventveto} +hasn't been called) or false otherwise (if it was). \membersection{wxNotifyEvent::Veto}\label{wxnotifyeventveto} @@ -50,3 +62,4 @@ Prevents the change announced by this event from happening. It is in general a good idea to notify the user about the reasons for vetoing the change because otherwise the applications behaviour (which just refuses to do what the user wants) might be quite surprising. +