Fix for time. ;-)

git-svn-id: http://www.villavu.com/repositories/merlijn/mufasa@126 3f818213-9676-44b0-a9b4-5e4c4e03d09d

Doc/mufasa_intro.tex

@@ -122,7 +122,7 @@ \section{The Window Class}
 a feature that allows the user to ``Lock'' the Windows' current data in
 Mufasa-maintained memory. \\
 
-Quick overview of functions:
+\subsection{Quick overview of functions}
 
 \begin{itemize}
 	\item ReturnData
@@ -138,6 +138,18 @@ \section{The Window Class}
 However; to fake user input, a programmer also needs the ability to 
 manipulate user input. Which brings us to the next MML Core class.
 
+\subsection{Freeze}
+
+The Window class also contains a feature called `Freeze'.
+Freeze allows one to save the current Client's Window data.
+All further methods that use the Client's Window data now use the saved
+data, until `UnFreeze' is called. \\
+
+This feature was easy to implement since we only had to modify the
+`ReturnData' method. If used wisely, this can speed up your program
+a lot, depending on the client size. It makes FindColorsTolerance about
+6 times faster on my system.
+
 \section{The Input Class}
 
 The \textbf{Input} Class is the class that takes care of all the input. \\

Known Issues.txt

@@ -2,7 +2,6 @@ Known issues:
 
 Linux:
 	- Mouse Clicking only works in the client, and the mouse click must be in the client, otherwise the event is ignored.
-	- CopyClientToBitmap isn't stable for IntArrPtr.
 
 Windows: