<div>I do not like mouseOverForKeyboardFocus verymuch.</div>
<div>It's to easy to lose the keyboard focus and then lose consentration.</div>
<div> </div>
<div>Cheers,</div>
<div>Karl</div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Fri, Jan 24, 2014 at 9:00 AM, Tim Felgentreff <span dir="ltr"><<a href="mailto:timfelgentreff@gmail.com" target="_blank">timfelgentreff@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Click-to-focus annoys me so much that it was one of the reasons I<br>switched from Mac to Linux on my MacBook back when I still had one.<br>
That being said, I'm fine with it being a preference that I can change<br>(an option Mac OS did not have.)<br><br>My reason for setting click-to-focus by default would be that in my<br>experience with undergrad students exposed to Squeak in the last few<br>
years, focus-follows-mouse has been a major issue for many. People who<br>know and want focus-follows-mouse tend to take a look if they can<br>enable it. I found that people who do not know there are different<br>focus behaviors than "what Windows/Mac/Unity does" don't look.<br>
<br>So, while I won't use it, in the interest of keeping the entry hurdle<br>low, I support switching to click-to-focus by default.<br><br>cheers<br>-Tim From: Ron Teitelbaum<br>Sent: 24/01/2014 04:18<br>To: The general-purpose Squeak developers list; <a href="mailto:ma.chris.m@gmail.com">ma.chris.m@gmail.com</a><br>
Subject: RE: [squeak-dev] mouseOverForKeyboardFocus default for 4.5<br>
<div class="HOEnZb">
<div class="h5"><br><br>> tim Rowledge<br>><br>><br>> On 23-01-2014, at 5:47 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>> > If hands are typing on the keyboard, the mouse is off to the side, so<br>
> > getting accidentally bumped would be pretty rare occurrence.<br>><br>> Actually I suspect otherwise. I've plenty of experience of a mouse cable<br>causing<br>> it to drift away from where it ought to be, or simply knocking it.<br>
<br>+1 happens all the time. I had to write code that centers the mouse when<br>the app starts so it would be on the screen, and code to move the mouse away<br>from menus when they are active just so that I can properly support menu<br>
keys. Seems like I'm always hacking the mouse to support simple behaviors.<br><br><br>><br>><br>> tim<br><br></div></div></blockquote></div><br>