Re: [FreeWRL-develop] touch vs navigation was Viewer grouping, finger navigation, landscape/portrait, and Re: Dave Jouberts UI code unification AND Mobile Navigation.

[doug s. <hig...@ho...>]

Thanks Dave, it's clearer now.
I want to take back what I said earlier about decomposing gestures.
And sounds like multiple-single touches never get through, so no need for a new 2-touch ScaleSensor node spec, 2-touch mode for RotationSensor, or being able to touch multiple sensors simaltaneously.
-Doug
 
> This is something to think about, but it is partially solved by
> convention on the Android.
>
> The 'gesture' engine intercepts the pinch before freewrl sees a touch,
> so one can always navigate outwards, and is a good reason to let an
> seperate engine recognise the gesture rather than handle it explicitly.
>
> Also, the menu button is implemented in hardware, so one always has an out.
>
> Dave
>
> On 30 May 2011 20:42, "doug sanden"
> >
> wrote:
> >
> >>
> >> I was doing things to help handle rotation of my iPhone, and
> upcoming Android platform; things that are required for our Wifi
> looking, and enhanced reality work on mobile devices.
> >>
> >>
> >> I *hope* that I'm going down the right path with my
> orientation-based view code - time will tell. I'm working on basic
> "EXAMINE" and "WALK" mode functionality right now, where one puts one
> finger on the screen and slides that finger.
> >>
> >
> > touch vs navigation:
> >
> > Have you ever navigated up too close to a big touch-sensor - like a
> door - you didn't want to touch, and struggled to navigate away? If
> it's filling the entire screen, there's no where to move the mouse to
> navigate. It's possible in the desktop version: you switch to Fly mode,
> launch a web browser, go to the freewrl commands page, and remind
> yourself of which keyboard keys are for Fly mode (not arrow keys). Then
> use those keys to 'fly' away from the touchsensor.
> >
> > On a small screen -like mobile- and with keyboard not as readily
> available- how do you get to the keyboard on iPhone? - it looks harder.
> >
> > So if you have a way to separate out what's for navigating, and
> what's for touching, and do that in the UI / frontend somehow, I
> suspect that would be very helpful in some touchsensor-rich scenes.
> >
> > -Doug
> >
> ------------------------------------------------------------------------------
> > vRanger cuts backup time in half-while increasing security.
> > With the market-leading solution for virtual backup and recovery,
> > you get blazing-fast, flexible, and affordable data protection.
> > Download your free trial now.
> > http://p.sf.net/sfu/quest-d2dcopy1
> > _______________________________________________
> > FreeWRL-develop mailing list
> >
> Fre...@li...
> > https://lists.sourceforge.net/lists/listinfo/freewrl-develop
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security. With the
> market-leading solution for virtual backup and recovery, you get
> blazing-fast, flexible, and affordable data protection. Download your
> free trial now. http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________ FreeWRL-develop mailing
> list Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freewrl-develop