Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
multitouch
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Taddeüs Kroes
multitouch
Commits
21750c65
Commit
21750c65
authored
Jun 26, 2012
by
Taddeus Kroes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Worked on report.
parent
7a0b1b32
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
10 additions
and
13 deletions
+10
-13
docs/data/diagrams.tex
docs/data/diagrams.tex
+5
-5
docs/report.tex
docs/report.tex
+5
-7
tests/parse_arguments.py
tests/parse_arguments.py
+0
-1
No files found.
docs/data/diagrams.tex
View file @
21750c65
...
...
@@ -254,11 +254,11 @@
\end{tikzpicture}
}
\caption
{
Two nested squares both listen to
rotation gestures. The two
figures both show a touch object triggering an event, which is
delegated through the event area tree in the order indicated by the
numbered arrow labels. Dotted arrows represent a flow of gestures,
regular arrows represent events.
Two nested squares both listen to
``tap'' gestures. The two figures
both show a touch object triggering an event, represented by a
black dot. The event is delegated through the event area tree in
the order indicated by the numbered arrow labels. Dotted arrows
re
present a flow of gestures, re
gular arrows represent events.
}
\label
{
fig:eventpropagation
}
\end{figure}
...
...
docs/report.tex
View file @
21750c65
...
...
@@ -378,11 +378,11 @@ detection for every new gesture-based application.
ideal tool to determine the order in which an event is delegated. Event
areas in deeper layers of the tree are positioned on top of their parent.
An object touching the screen is essentially touching the deepest event
area in the tree that contains the triggered event.
That event area should
be the first to delegate the event to its gesture detection components, and
then propagate the event up in the tree to its ancestors. A gesture
detection component can stop the propagation of the event by its
corresponding event area.
area in the tree that contains the triggered event.
A gesture detection
component can stop the propagation of the event by its corresponding event
area.
\eventpropagationfigure
An additional type of event propagation is ``immediate propagation'', which
indicates propagation of an event from one gesture detection component to
...
...
@@ -393,8 +393,6 @@ detection for every new gesture-based application.
propagation of an event, so that the event is not passed to the next
gesture detection component, nor to the ancestors of the event area.
\eventpropagationfigure
The concept of an event area is based on the assumption that the set of
originating events that form a particular gesture, can be determined based
exclusively on the location of the events. This is a reasonable assumption
...
...
tests/parse_arguments.py
View file @
21750c65
...
...
@@ -18,7 +18,6 @@ def create_parser():
def
parse_args
(
parser
):
print
'here:'
,
parser
.
format_usage
()
args
=
parser
.
parse_args
()
# Configure logger
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment