middle button so a portable application should avoid relying on the events from
it.
+For the \texttt{wxEVT\_ENTER\_WINDOW} and \texttt{wxEVT\_LEAVE\_WINDOW} events
+purposes, the mouse is considered to be inside the window if it is in the
+window client area and not inside one of its children. In other words, the
+parent window receives \texttt{wxEVT\_LEAVE\_WINDOW} event not only when the
+mouse leaves the window entirely but also when it enters one of its children.
+
{\bf NB:} Note that under Windows CE mouse enter and leave events are not natively supported
by the system but are generated by wxWidgets itself. This has several
drawbacks: the LEAVE\_WINDOW event might be received some time after the mouse
\constfunc{int}{GetWheelRotation}{\void}
Get wheel rotation, positive or negative indicates direction of
-rotation. Current devices all send an event when rotation is equal to
-+/-WheelDelta, but this allows for finer resolution devices to be
-created in the future. Because of this you shouldn't assume that one
-event is equal to 1 line or whatever, but you should be able to either
-do partial line scrolling or wait until +/-WheelDelta rotation values
-have been accumulated before scrolling.
+rotation. Current devices all send an event when rotation is at least
++/-WheelDelta, but finer resolution devices can be created in the future.
+Because of this you shouldn't assume that one event is equal to 1 line, but you
+should be able to either do partial line scrolling or wait until several
+events accumulate before scrolling.
\membersection{wxMouseEvent::GetWheelDelta}\label{wxmouseeventgetwheeldelta}