Because its easier, quicker and keeps constancy with the entire roter method. 
Why swipe left or right when you can move your finger round until you find what 
you want. Sighted people don't swipe that way. 

A good system will try to have more than 1 way to do something as people have 
different likes and methods. 

Personally, I like the edit roter as even though I can do it another way, I 
find it quicker and I'm very used to using the roter all the time. 

Danny. 

Sent from my iPhone

On 27/01/2013, at 9:51 PM, "Christopher-Mark Gilland" <clgillan...@gmail.com> 
wrote:

> OK, this might seem like a really odd question, but hear me out here.
> 
> What is the point of the edit rotor option when in a text box?  Before you 
> start explaining to me what it does, no no no... that's not what I'm asking. 
> I know what it does!, but, why?
> 
> See, here's the thing...  If you are on a text field, or honestly, for that 
> mind, a text message, etc. if you double tap on the content, and leave your 
> finger on the screen after the second tap, then after hearing the 3 little 
> pass gesture through bleep tone, you then lift your finger, you'll hear 
> another little popup sound.  It's the same sound you get when I O S is trying 
> to auto-correct.  Now, if you flick right from that text box, text message, 
> etc. etc. you'll see that right there you have menu options like select, 
> select all, copy, paste, etc.  And before anyone says, yeah, but tapping on 
> them doesn't work, that's why you need the rotor... Oh, you wanna make a bet 
> they don't work?  I just did it over here, and they work perfectly!  I can't 
> figure out in the edit rotor setting nor in this method how to select a 
> portion of text without selecting all.  We had this discussion once on list, 
> about pinching in and out to select, but no matter what I try, and apparently 
> by far I'm not the only one who's had issues, I can't get it to work 
> regardless what I do.  Anyway, that's not the point. Point being, why make a 
> rotor setting for this stuff, when doing it the non-voiceover way like 
> normal... pardon the pun, sighted people would do, works perfectly?  Isn't 
> that kind of a waiste of source code?  What 'em I missing here?  Just seems a 
> bit redundant.  Is it more just a preference thing one may like doing it one 
> way where another might like the other way, or is there actually a specific 
> reason why to do one over the other?
> 
> Chris. 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To post to this group, send email to macvisionaries@googlegroups.com.
> To unsubscribe from this group, send email to 
> macvisionaries+unsubscr...@googlegroups.com.
> Visit this group at http://groups.google.com/group/macvisionaries?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to