|
|
@@ -2,10 +2,11 @@
|
|
|
|
|
|
\usepackage[english]{babel}
|
|
|
\usepackage[utf8]{inputenc}
|
|
|
+\usepackage[usenames,dvipsnames]{xcolor}
|
|
|
\usepackage{amsmath,hyperref,graphicx,booktabs,float}
|
|
|
|
|
|
% Link colors
|
|
|
-\hypersetup{colorlinks=true,linkcolor=black,urlcolor=blue}
|
|
|
+\hypersetup{colorlinks=true,linkcolor=black,urlcolor=blue,citecolor=OliveGreen}
|
|
|
|
|
|
\title{Bachelor thesis\\Universal multi-touch event mechanism}
|
|
|
\author{\begin{tabular}{ll}
|
|
|
@@ -112,11 +113,11 @@ To design such a mechanism properly, the following questions are relevant:
|
|
|
|
|
|
\subsubsection{The TUIO protocol}
|
|
|
|
|
|
- The TUIO protocol\footnote{\url{http://tuio.org/?specification}}
|
|
|
- defines a way to geometrically describe tangible objects, such as
|
|
|
- fingers or fiducials on a multi-touch table. The table used for this
|
|
|
- thesis uses the protocol in its driver. Object information is sent to
|
|
|
- the TUIO UDP port (3333 by default).
|
|
|
+ The TUIO protocol \cite{TUIO_KBBC05} defines a way to geometrically
|
|
|
+ describe tangible objects, such as fingers or fiducials on a
|
|
|
+ multi-touch table. The table used for this thesis uses the protocol in
|
|
|
+ its driver. Object information is sent to the TUIO UDP port (3333 by
|
|
|
+ default).
|
|
|
|
|
|
For efficiency reasons, the TUIO protocol is encoded using the Open
|
|
|
Sound Control
|
|
|
@@ -153,18 +154,15 @@ To design such a mechanism properly, the following questions are relevant:
|
|
|
TUIO coordinates range from $0.0$ to $1.0$, with $(0.0, 0.0)$ being the
|
|
|
left top corner of the screen and $(1.0, 1.0)$ the right bottom corner.
|
|
|
To focus events within a window, a translation to window coordinates is
|
|
|
- required in the client application, as stated by the
|
|
|
- specification:
|
|
|
- \begin{citation}
|
|
|
+ required in the client application, as stated by the online
|
|
|
+ specification \cite{TUIO_specification}:
|
|
|
+ \begin{quote}
|
|
|
In order to compute the X and Y coordinates for the 2D profiles a
|
|
|
TUIO tracker implementation needs to divide these values by the
|
|
|
actual sensor dimension, while a TUIO client implementation
|
|
|
consequently can scale these values back to the actual screen
|
|
|
dimension.
|
|
|
- \end{citation}
|
|
|
-
|
|
|
- % TODO: change citation above to page from reference below
|
|
|
- test cite: \cite{TUIO_KBBC05}
|
|
|
+ \end{quote}
|
|
|
|
|
|
\subsection{Experiments}
|
|
|
|