[x3d-public] passive vs. active mouse isOver event

[Joe D Williams]

How about when the touch is animated away from the pointer. Should 
isover fo off, of stay on until the pointer is moved? What if another 
touch moves over the first?
What ever the spec history, what about Octaga? we need to recognize BS 
as the leading implementation and be sure to ask them. This should be 
a test.
Also, maybe more like a collision sensor. That is how I used the 
pointer when I expected that when an anchor moved under the pointer, 
then the link was live. In real life it doesn't matter which has 
moved, if there is a touch sensor, then it has to be evaluated each 
frame. That is what I learned from flux and bs.

Also, part of accessibility.
Maybe I have a good intention and wish to help the user by offering 
choices by moving them under the pointer? Sure, you may need a click, 
but, with a simple animation, shouldn't I be able to move the touch to 
get a hover?

OK, maybe this is hard to do in DOM, but DOM never had to deal with 
this, in the sense of 3D.

So, the best browsers have shown how to do it in X3D, To me there is 
no doubt that the #X3D spec should say the isover reported no matter 
what has moved.
For <x3d> then it seems like an open issue.

Ya know in the xflow spec at the beginning, it says that the VRML guys 
didn't pick html...
Really, the VRML guys didn't pick the DOM. The DOM is (still) so far 
from SAI and X3D scene processing model that even simple things like 
this are hard. whatever the marker is, it is not a 2D cursor anymore, 
it is a 3D pointer, which can take many forms and should be as 
realistic as possible. It is a touchsensor and when touching, you what 
it to be live, not delayed until i make a movement, or whatever, 
anyway maybe silly, but an important little detail about how we 
represent the environment and our interactions with it,

Thanks and Best,
Joe







f----- Original Message ----- 
From: "Don Brutzman" <brutzman at nps.edu>
To: "Andreas Plesch" <andreasplesch at gmail.com>; "X3D Graphics public 
mailing list" <x3d-public at web3d.org>
Sent: Monday, November 07, 2016 9:09 AM
Subject: Re: [x3d-public] passive vs. active mouse isOver event


> On 11/5/2016 2:46 PM, Andreas Plesch wrote:
>> I noticed that cobweb does not generate an isOver TouchSensor event 
>> when the pointing device is not moved actively but the sensed 
>> geometry itself moves under the mouse pointer. At first this was 
>> surprising to me but after reading
>>
>> http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/pointingsensor.html#TouchSensor
>>
>> this seems to be the expected behaviour since active mouse movement 
>> is required to generate events.
>
> ======================================================
> The isOver field reflects the state of the pointing device with 
> regard to whether it is pointing towards the TouchSensor node's 
> geometry or not. When the pointing device changes state from a 
> position such that its bearing does not intersect any of the 
> TouchSensor node's geometry to one in which it does intersect 
> geometry, an isOver TRUE event is generated. When the pointing 
> device moves from a position such that its bearing intersects 
> geometry to one in which it no longer intersects the geometry, or 
> some other geometry is obstructing the TouchSensor node's geometry, 
> an isOver FALSE event is generated. These events are generated only 
> when the pointing device has moved and changed `over' state. Events 
> are not generated if the geometry itself is animating and moving 
> underneath the pointing device.
> ======================================================
>
>> Do other browser behave the same way ?
>
> yes good question, glad people are checking...
>
> I wondered if we should add a boolean field for this, but it seems 
> clear that user interaction is an intended prerequisite for 
> TouchSensor activity (i.e. "touching").   If an author wants 
> something to occur when geometry becomes visible, they can use 
> VisibilitySensor instead.
>
> all the best, Don
> -- 
> Don Brutzman  Naval Postgraduate School, Code USW/Br 
> brutzman at nps.edu
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA 
> +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics 
> http://faculty.nps.edu/brutzman
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org