[x3d-public] Avatar Handling / non-standard movement strategies/ input of key strokes ------ Was: Mac-unaware PageUp/PageDown, Viewpoint list, navigation keys?

[Joseph D Williams]

Hi Christoph, 
I didn’t study lately, but isn’t there something about picking in there now.?

www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html
Joe


From: Christoph Valentin
Sent: Thursday, January 17, 2019 4:32 PM
To: x3d-public at web3d.org
Subject: Re: [x3d-public] Avatar Handling / non-standard movement strategies/ input of key strokes ------ Was: Mac-unaware PageUp/PageDown,Viewpoint list, navigation keys?

And again I have been too emotional :(

So sorry for that.

When it comes to my ideas, then I am feeling like a mother for her children. 

Please ignore the emotional stuff :-)

-- 
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 17.01.19, 19:19, Christoph Valentin <christoph.valentin at gmx.at> schrieb:
Hi all,
 
I hope I was not too intrusive. I could not resist to phrase the idea, which came to my mind due to the discussion, which Don started.
 
Should we discuss it? Is my intention clear?
 
Is it redundant? Is it too brilliant? Is it old stuff?
 
Thanks about ANY feed back.
 
Christoph
Hi all
Sorry for writing so many e-mails for just one idea. Now I have seized the lunch break to summarize the suggestion, maybe it can explain the idea better:
1. Is there anything in X3D that makes the following DRAFT proposal obsolete?
2. DRAFT Proposal for simplified handling of keystrokes or other input of character streams via KeySensor and StringSensor.
a) Each X3D grouping node defines two additional fields
<field accessType='inputOutput' name='canHaveFocus' type='SFBool' value='false'/>
<field accessType='inputOutput' name='isAvatar' type='SFBool' value='false'/>
b) the behaviour is as follows:
b.1) canHaveFocus == false: well-known "old" behaviour, no change
b.2) canHaveFocus == true && isAvatar == false: the browser may select this group together with all static and dynamic children to get the "focus" by some means. Only one group and its children can have the focus at any time. Having the focus means all StringSensor nodes and KeySensor nodes contained in the group are enabled regardless of the value of their "enabled" field. The browser SHOULD graphically indicate, which geometry has got the focus, e.g. by highlighting or by drawing a 2-dimensional "frame" around the geometry.
b.3) canHaveFocus == true && isAvatar == true: same behaviour as with b.2), but the avatar gets the focus any time, when no other geometry has the focus, even, if the avatar is invisible currently.
Have a nice day
Christoph
Gesendet: Donnerstag, 17. Januar 2019 um 09:44 Uhr
Von: "Christoph Valentin" <christoph.valentin at gmx.at>
An: "Christoph Valentin" <christoph.valentin at gmx.at>, "Leonard Daly" <Leonard.Daly at realism.com>, x3d-public at web3d.org
Betreff: Re: [x3d-public] Mac-unaware PageUp/PageDown, Viewpoint list, navigation keys?
Maybe its silly, but I thought: 1) I can *ride* a locomotive and * use* its controls or 2) I can *be* a locomotive

Like a Horse + Rider = a single entity
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 17.01.19, 09:28, Christoph Valentin <christoph.valentin at gmx.at> schrieb: 
Plus a "special handling" for avatars, where the pilot avatar can have an "always on" focus to supersede Standard navigation by avatar specific movement Strategy..........
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 17.01.19, 07:45, Christoph Valentin <christoph.valentin at gmx.at> schrieb: 
Each grouping node would need a new field:

<field accessType='inputOutput' type='SFBool' name='canHaveFocus' value='false'/>

and the rest was up to the browser.
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 17.01.19, 07:25, Christoph Valentin <christoph.valentin at gmx.at> schrieb: 
And what about a concept of "having the focus":

If a grouping node "had the focus", then all KeySensor and StringSensor nodes within this group would become "enabled".

KR
Christoph
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 16.01.19, 23:22, Christoph Valentin <christoph.valentin at gmx.at> schrieb: 
Maybe my opinion is not important, but I think these concrete hints which key to use for which navigation function should be completely avoided in X3D Spec.

Isn't it enough to have the abstract/virtual concepts of "indicating forward/backward/left/right/up/down", "fast/slow", "touch", "drag" by "some means that are up to the Browser"?

The Events that are created by the sensor nodes have to be specified well, on the other hand. 

A different story is the Network Sensor, where the protocol should be specified to the bits. 

Just my opinion and just Two Cent:-)
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
 
_______________________________________________ x3d-public mailing list x3d-public at web3d.org http://web3d.org/mailman/listinfo/x3d-public_web3d.org 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190118/80dd842f/attachment-0001.html>