|
@@ -18,8 +18,8 @@ both x and y by 8 (and add 1 if you want to have it 1 based).
|
|
|
|
|
|
|
|
\item The real resolution of graphic modes and the one the mouse driver uses can
|
|
\item The real resolution of graphic modes and the one the mouse driver uses can
|
|
|
differ. For example, mode 13h (320*200 pixels) is handled by the mouse driver
|
|
differ. For example, mode 13h (320*200 pixels) is handled by the mouse driver
|
|
|
-as 640*200, so you will have to multiply the coordinates you give to the
|
|
|
|
|
-driver and divide the ones you get from it by 2.
|
|
|
|
|
|
|
+as 640*200, so you will have to multiply the X coordinates you give to the
|
|
|
|
|
+driver and divide the ones you get from it by 2 in that mode.
|
|
|
|
|
|
|
|
\item By default the mouse unit is compiled with the conditional define
|
|
\item By default the mouse unit is compiled with the conditional define
|
|
|
MouseCheck. This causes every procedure/function of the unit to check the
|
|
MouseCheck. This causes every procedure/function of the unit to check the
|
|
@@ -29,7 +29,7 @@ mouse is found, you can recompile the mouse unit without this conditional
|
|
|
define.
|
|
define.
|
|
|
|
|
|
|
|
\item
|
|
\item
|
|
|
-You will notice that several procedures/functinos have longint sized
|
|
|
|
|
|
|
+You will notice that several procedures/functions have longint sized
|
|
|
parameters while only the lower 16 bits are used. This is because FPC is
|
|
parameters while only the lower 16 bits are used. This is because FPC is
|
|
|
a 32 bit compiler and consequently 32 bit parameters result in faster code.
|
|
a 32 bit compiler and consequently 32 bit parameters result in faster code.
|
|
|
\end{itemize}
|
|
\end{itemize}
|
|
@@ -168,7 +168,7 @@ botto-right corner at (\var{xmax,ymax}),which causes the mouse cursor to be
|
|
|
turned off when it is moved into it.
|
|
turned off when it is moved into it.
|
|
|
|
|
|
|
|
When the mouse is moved into the specified region, it is turned off until you
|
|
When the mouse is moved into the specified region, it is turned off until you
|
|
|
-call \var{ShowMouse} again. However, when you've called \seep{ShowMouse}, you'll have to
|
|
|
|
|
|
|
+call \var{ShowMouse} again. However, once you've called \seep{ShowMouse}, you'll have to
|
|
|
call \var{SetMouseHideWindow} again to redefine the hide window...
|
|
call \var{SetMouseHideWindow} again to redefine the hide window...
|
|
|
This may be annoying, but it's the way it's implemented in the mouse driver.
|
|
This may be annoying, but it's the way it's implemented in the mouse driver.
|
|
|
|
|
|
|
@@ -177,8 +177,8 @@ only the lower 16 bits are used.
|
|
|
}{None.}{\seep{ShowMouse}, \seep{HideMouse}}
|
|
}{None.}{\seep{ShowMouse}, \seep{HideMouse}}
|
|
|
|
|
|
|
|
|
|
|
|
|
-\latex{nputlisting{mouseex/mouse1.pp}}
|
|
|
|
|
-\html{\input{mouseex/mouse1.tex}}
|
|
|
|
|
|
|
+\latex{nputlisting{mouseex/mouse9.pp}}
|
|
|
|
|
+\html{\input{mouseex/mouse9.tex}}
|
|
|
|
|
|
|
|
\procedure{SetMousePos}{(x,y:Longint)}{
|
|
\procedure{SetMousePos}{(x,y:Longint)}{
|
|
|
\var{SetMosusePos} sets the position of the mouse cursor on the screen.
|
|
\var{SetMosusePos} sets the position of the mouse cursor on the screen.
|
Jonas Maebe