enabled for certain type of
nodes such buttons or other classic controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external link)
Hello
: discussion about touch events
(Now my answer using external link)
Hello Daniel,
this is quite similar to my idea described earlier. The major
difference is the fair division of capture zones among
siblings. It's an interesting idea, let's explore it. What pops
first is that children can also
be
selectively enabled for certain type of nodes such buttons or
other classic controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using
Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external link)
Hello Daniel,
this is quite similar to my idea described earlier. The major
difference is the fair division
I'm only occasionally skimming this thread so I hope I don't disrupt
discussions by throwing in a few observations now and then...
On 11/20/2013 7:30 AM, Assaf Yavnai wrote:
Pavel,
I think that this is a very good example why touch events should be processed
separately from mouse events.
For
Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external link)
Hello Daniel,
this is quite similar to my idea described earlier. The major
difference is the fair division
of nodes such buttons or other classic
controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external link)
Hello Daniel,
this is quite
be
selectively enabled for certain type of nodes such buttons or other classic
controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external
feature should be selectively enabled for certain type of nodes such
buttons or other classic controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch
or other classic controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external link)
Hello Daniel,
this is quite similar to my idea
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my answer using external link)
Hello Daniel,
this is quite similar to my idea described earlier. The major difference is the
fair division of capture zones among siblings. It's
be selectively enabled for certain type of nodes such buttons
or other classic controls.
Regards,
Seeon
-Original Message-
From: Pavel Safrata
Sent: Tuesday, November 12, 2013 1:11 PM
To: Daniel Blaukopf
Cc: OpenJFX
Subject: Re: discussion about touch events
(Now my
The image seems to have been stripped somewhere, trying to attach once more.
Pavel
On 12.11.2013 11:46, Pavel Safrata wrote:
Hello Daniel,
this is quite similar to my idea described earlier. The major
difference is the fair division of capture zones among siblings.
It's an interesting idea,
(My original message didn't get through to openjfx-dev because I used
inline images. I've replaced those images with external links)
On Nov 11, 2013, at 11:30 PM, Pavel Safrata pavel.safr...@oracle.com
mailto:pavel.safr...@oracle.com wrote:
On 11.11.2013 17:49, Tomas Mikula wrote:
On Mon,
Daniel, Pavel ,
I tend to agree with both of you and also to add some ideas and comments:
1) I think that touch picker and mouse picker should be different
implementations used according to origin of event. This means that if
application is written to listen only to mouse events and its
The ascii sketch looked fine on my screen before I sent the mail :( I
hope the idea is clear from the text
(now in the reply dialog its also look good)
Assaf
On 11/11/2013 12:51 PM, Assaf Yavnai wrote:
Hi Guys,
I hope that I'm right about this, but it seems that touch events in
glass are
Hi Assaf,
this was discussed during during the multi-touch API design phase. I
completely understand what you are saying, yet it has no
straightforward/automatic solution you may have imagined. First, we
can't pick whatever falls into the circle - imagine there are two
buttons next to each
I see the need to be aware of the area that is covered by fingers rather
than just considering that area's center point.
I'd guess that this adds a new layer of complexity, though. For instance:
Say we have a button on some background and both the background and the
button do have an onClick
On Mon, Nov 11, 2013 at 1:28 PM, Philipp Dörfler phdoerf...@gmail.com wrote:
I see the need to be aware of the area that is covered by fingers rather
than just considering that area's center point.
I'd guess that this adds a new layer of complexity, though. For instance:
Say we have a button
On 11.11.2013 17:49, Tomas Mikula wrote:
On Mon, Nov 11, 2013 at 1:28 PM, Philipp Dörfler phdoerf...@gmail.com wrote:
I see the need to be aware of the area that is covered by fingers rather
than just considering that area's center point.
I'd guess that this adds a new layer of complexity,
20 matches
Mail list logo
