mirror of
https://github.com/moparisthebest/Simba
synced 2024-11-26 03:02:15 -05:00
Less images pl0x
git-svn-id: http://www.villavu.com/repositories/merlijn/mufasa@503 3f818213-9676-44b0-a9b4-5e4c4e03d09d
This commit is contained in:
parent
f181f866e3
commit
5fc1677442
@ -96,7 +96,8 @@ detailed exception.
|
||||
|
||||
\subsection{How to Handle Exceptions}
|
||||
|
||||
An exception is handled with a $try$ ... $except$ ... $finally$ statement.
|
||||
An exception is handled with a \textbf{try} ... \textbf{except}
|
||||
... \textbf{finally} statement.
|
||||
See the example in the previous section for more details.
|
||||
|
||||
\chapter{Input}
|
||||
@ -109,15 +110,15 @@ A few variables are exported for working with Mufasa Mouse Functions.
|
||||
|
||||
TClickType, which defines the click type.
|
||||
\begin{itemize}
|
||||
\item $mouse\_Right = 0$
|
||||
\item $mouse\_Left = 1$
|
||||
\item $mouse\_Middle = 2$
|
||||
\item \textbf{mouse\_Right} = 0
|
||||
\item \textbf{mouse\_Left} = 1
|
||||
\item \textbf{mouse\_Middle} = 2
|
||||
\end{itemize}
|
||||
|
||||
TMousePress, which defines if the mouse button is to be down or up.
|
||||
\begin{itemize}
|
||||
\item $mouse\_Up$
|
||||
\item $mouse\_Down$
|
||||
\item \textbf{mouse\_Up}
|
||||
\item \textbf{mouse\_Down}
|
||||
\end{itemize}
|
||||
|
||||
% TClickType = (mouse_Left, mouse_Right, mouse_Middle);
|
||||
@ -133,25 +134,26 @@ MoveMouse moves the mouse pointer to the specified x and y coordinates.
|
||||
\textbf{procedure} {\color{blue}{GetMousePos}}({\color{typeRed}
|
||||
{out x, y: }}{\color{typeGreen}{Integer}});
|
||||
|
||||
GetMousePos returns the current position of the mouse in $x$ and $y$.
|
||||
GetMousePos returns the current position of the mouse in \textbf{x} and
|
||||
\textbf{y}.
|
||||
|
||||
\subsection{HoldMouse}
|
||||
\textbf{procedure} {\color{blue}{HoldMouse}}({\color{typeRed}
|
||||
{x, y: }}{\color{typeGreen}{Integer}}; {\color{typeRed}{clickType :}}
|
||||
{\color{typeGreen}{TClickType}})
|
||||
|
||||
HoldMouse holds the given mouse button (clickType) down at the specified $x$, $y$
|
||||
coordinate. If the mouse if not at the given $x$, $y$ yet, the mouse position
|
||||
will be set to $x$, $y$.
|
||||
HoldMouse holds the given mouse button (clickType) down at the specified \textbf{x}, \textbf{y}
|
||||
coordinate. If the mouse if not at the given \textbf{x}, \textbf{y} yet, the mouse position
|
||||
will be set to \textbf{x}, \textbf{y}.
|
||||
|
||||
\subsection{ReleaseMouse}
|
||||
\textbf{procedure} {\color{blue}{ReleaseMouse}}({\color{typeRed}
|
||||
{x, y: }}{\color{typeGreen}{Integer}}; {\color{typeRed}{clickType :}}
|
||||
{\color{typeGreen}{TClickType}});
|
||||
|
||||
ReleaseMouse releases the given mouse button (clickType) at the specified $x$, $y$
|
||||
coordinate. If the mouse if not at the given $x$, $y$ yet, the mouse position
|
||||
will be set to $x$, $y$.
|
||||
ReleaseMouse releases the given mouse button (clickType) at the specified \textbf{x}, \textbf{y}
|
||||
coordinate. If the mouse if not at the given \textbf{x}, \textbf{y} yet, the mouse position
|
||||
will be set to \textbf{x}, \textbf{y}.
|
||||
|
||||
\subsection{ClickMouse}
|
||||
\textbf{procedure} {\color{blue}{ClickMouse}}({\color{typeRed}
|
||||
@ -359,7 +361,7 @@ Virtual Keys also work on non-Windows operating systems.
|
||||
|
||||
KeyDown sends a request to the Operating System to ``fake'' an event that
|
||||
causes the Key to be ``down''.
|
||||
$key$ can be any Virtual Key\footnote{See the section on Virtual Keys}.
|
||||
\textbf{key} can be any Virtual Key\footnote{See the section on Virtual Keys}.
|
||||
|
||||
\subsubsection{Common pitfalls}
|
||||
|
||||
@ -372,7 +374,7 @@ is down as well.
|
||||
|
||||
KeyUp sends a request to the Operating System to ``fake'' an event that
|
||||
causes the Key to be ``up''.
|
||||
$key$ can be any Virtual Key.
|
||||
\textbf{key} can be any Virtual Key.
|
||||
|
||||
\subsection{PressKey}
|
||||
|
||||
@ -386,7 +388,7 @@ PressKey combines KeyDown and KeyUp, to fake a key press.
|
||||
\textbf{procedure} {\color{blue}{SendKEys}}({\color{typeRed}
|
||||
{s: }}{\color{typeGreen}{String}});
|
||||
|
||||
SendKeys takes a string $s$, and attempts to send it's complete contents to
|
||||
SendKeys takes a string \textbf{s}, and attempts to send it's complete contents to
|
||||
the client. It currently only accepts characters ranging from ``A..z''.
|
||||
|
||||
\subsection{IsKeyDown}
|
||||
@ -483,7 +485,7 @@ Deprecated DTM type:
|
||||
{\color{typeGreen}{Integer}}) {\color{typeGreen}{: Boolean}}; \\
|
||||
|
||||
FindDTM is the most basic DTM finding function. It takes a box to search in,
|
||||
and if the DTM is found, it will set $x$ and $y$ to the coordinate the DTM
|
||||
and if the DTM is found, it will set \textbf{x} and \textbf{y} to the coordinate the DTM
|
||||
was found at and it will also return true. Else, it returns false.
|
||||
Once a DTM is found, it will stop searching. In other words; it always returns
|
||||
the first found DTM.
|
||||
@ -494,8 +496,8 @@ the first found DTM.
|
||||
{\color{typeGreen}{Integer}}; {\color{typeRed}{Var Points: }}
|
||||
{\color{typeGreen}{TPointArray}}){\color{typeGreen}{: Boolean}}; \\
|
||||
|
||||
FindDTMs is like FindDTM, but it returns an array of $x$ and $y$, as the
|
||||
$TPointArray$ type.
|
||||
FindDTMs is like FindDTM, but it returns an array of \textbf{x} and \textbf{y}, as the
|
||||
\textbf{TPointArray} type.
|
||||
|
||||
\subsection{FindDTMRotated}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user