From 03d7db74bfa3321d3be6a83048aaae9ed34a3882 Mon Sep 17 00:00:00 2001 From: Thomas Pietrzak Date: Mon, 15 Nov 2021 18:17:36 +0100 Subject: [PATCH] Fixed clearpages --- hdrmain.tex | 51 ++++++++++++------------------------------------- tex/0-titre.tex | 2 -- tex/3-input.tex | 10 +++++----- 3 files changed, 17 insertions(+), 46 deletions(-) diff --git a/hdrmain.tex b/hdrmain.tex index c2ea5dc..352657c 100644 --- a/hdrmain.tex +++ b/hdrmain.tex @@ -1,5 +1,5 @@ % !TEX program = xelatex -\documentclass[11pt,a4paper,twoside,titlepage,openbib]{phdthesis} +\documentclass[11pt,a4paper,twoside,titlepage,openbib,openright]{phdthesis} \usepackage{getcommit} \usepackage{xstring} @@ -11,52 +11,25 @@ \author{\Large Thomas Pietrzak} \date{} -\includeonly{tex/0-titre,tex/3-input} +%\includeonly{tex/0-titre,tex/3-input} \begin{document} \frontmatter -\include{tex/0-titre} + \include{tex/0-titre} + \include{tex/00-tocs.tex} + \include{tex/00-remerciements} -\include{tex/00-tocs.tex -} -\include{tex/00-remerciements} - \cleardoublepage + \mainmatter -\mainmatter + \include{tex/1-introduction} + \include{tex/2-output} + \include{tex/3-input} + \include{tex/4-loop} + \include{tex/5-conclusion} -\include{tex/1-introduction} - \cleardoublepage - -\include{tex/2-output} - \cleardoublepage - -\include{tex/3-input} - \cleardoublepage - -\include{tex/4-loop} - \cleardoublepage - - -%\input{tex/relatedwork} -% \cleardoublepage - -% \input{tex/perceptionaction} -% \cleardoublepage - -% \input{tex/directmanipulation} -% \cleardoublepage - -% \input{tex/controlautomation} -% \cleardoublepage - -%\input{tex/something} -% \cleardoublepage - -\include{tex/5-conclusion} - -\backmatter + \backmatter \printindex diff --git a/tex/0-titre.tex b/tex/0-titre.tex index 3a6a506..f3d460a 100644 --- a/tex/0-titre.tex +++ b/tex/0-titre.tex @@ -123,5 +123,3 @@ \end{titlepage} \newgeometry{inner=1.5cm, outer=2.5cm, vmargin=3cm} - - \cleardoublepage diff --git a/tex/3-input.tex b/tex/3-input.tex index f29a9fd..c916918 100644 --- a/tex/3-input.tex +++ b/tex/3-input.tex @@ -327,7 +327,7 @@ Other methods enable repetitive measures, but they are adapted to specific input %Latency has long been known to affect performance and user perception in indirect pointing tasks, Virtual Reality and touch interactions [1, 8–10, 12, 13, 16, 21]. While today’s touchscreens show latencies ranging from 50 to 200 ms [14], it is known that users can perceive touchscreen latency as low as 2 ms [14] and that performance for dragging tasks degrades above 25 ms [10]. In indirect interaction, latencies above 50 ms are noticed and affect performance [8, 9]. %Considering the importance of latency in interactive systems, it is essential to measure and report it, to assess how it af- fects users or the results of an experiment. Until recently, its measure has been a tedious process based on the use of external cameras [11, 14, 15, 18–21] but methods have been proposed to ease the process through interactive tools [2, 6] or repeated measures [3, 7]. These tools can be used to try to reduce latency but it can be a trial and error process without the understanding of the influence of each part of a system. In addition, none of the measurement tools allows to measure end-to-end latency while a user interacts with the system, and existing tools are limited to specific technologies. -\paragraph{Measurement apparatus} +\subsubsection{Measurement apparatus} We designed LagMeter, a latency measurement tool that facilitates repetitive measures, and enables the slicing of latency between several parts of the interactive system~\cite{casiez17}. It measures latency for any tap-based input such as keyboards, mice, touchpads, touchscreens. @@ -352,7 +352,7 @@ Then, a photodiode on the electronic board detects changes on the screen and the %Our method is usable with any tap-based input: keyboard, mouse, touchpad, touchscreen. %Slicing of latency with software probes. -\paragraph{Results and discussion} +\subsubsection{Results and discussion} What I realized with this project is that nothing in interaction can be considered as instantaneous. When we measured the responsiveness of the piezoelectric vibration sensor, we noticed that even the mechanical contact of a physical button creates latency at the millisecond scale. @@ -425,7 +425,7 @@ Not only this extended input vocabulary can be used to map brush parameters. But it also enables selecting commands and offer richer interactions, whether it is with combinations of pen and touch interactions~ or by leveraging physical attributes of the pen~\cite{vogel11}. In this work we were interested in the bending of a flexible pen as additional degrees of freedom. -\paragraph{Prototypes} +\subsubsection{Prototypes} We built two series of prototypes, the first one being \emph{FlexStylus}~\cite{fellion16,fellion17} (\reffig{fig:penprototypes}, up). It used a custom flexion sensor made with 4 eroded fiber optics, with an infrared LED on one end and phototransistors on the other end each. @@ -466,7 +466,7 @@ We addressed this issue with the HyperBrush prototypes be adding a fake button t The relief of this button helped users keeping the stylus in a consistent orientation eyes-free. -\paragraph{Pen grips} +\subsubsection{Pen grips} Studies in the literature show that there is a strong connection betweeen the way users hold a stylus and the way they use the stylus~\cite{song11,hinckley13}. They noticed that participants in their user studies often changed the way they gripped the stylus depending on the task they were performing. @@ -502,7 +502,7 @@ However, we want to let such serendipitous behaviour happening because it makes -\paragraph{Flexural stiffness} +\subsubsection{Flexural stiffness} \input{figures/flexuralstiffnesses.tex} -- 2.30.2