11.3.0 build 7 released, for XO-1.75, XO-1.5 and XO-1

[Paul Fox]

kevin wrote:
 > On Tue, Sep 27, 2011 at 8:31 AM, Peter Robinson <pbrobinson at gmail.com>wrote:
 > 
 > > The "Come as you are? Oh Nevermind" release.
 > >
 > > We're into Activity freeze so no major changes.
 > >
 > > Download from:
 > >
 > > http://build.laptop.org/11.3.0/os7/
 > >
 > > Bugz fixed:
 > > Tap-to-click on AVC touchpads disabled
 > >
 > 
 > Folks:
 > 
 > Should I assume from the fix list that the tap-to-click which is running on
 > all 150 of our XO 1.5's using stable build 11-2 is an unintended
 > manufacturing/assembiy 'feature' of the newer trackpad production; i.e., a
 > bug, and not a desired feature?

when we introduced the synaptics touchpad (to replace the extremely
troublesome, and decreasingly available ALPS pad on XO-1), we
discovered that it did tap-to-click by default.  reaction was somewhat
split -- as you say, some users like it, but feedback from deployments
said that children tended to find it extremely confusing:  actions
that they intended to simply cause motion would cause something
altogether different to happen, and it was difficult for them to
understand why.  so we went to some effort to disable tap-to-click on
synaptics.

then the AVC touchpads were introduced, as an optional second-source
for the manufacturer to use.  OLPC of course approves such changes,
but the user-interface impact slipped past us at the time.  the AVC
pads also enable tap-to-click by default, and for uniformity we should
have disabled it by default.  but it require a different command
sequence for disabling, and for various reasons the change didn't
happen until today's os7.

so the answer to your question is yes, the presence of tap-to-click on
your laptops is unintended.

 > Some of our users were now liking the similarity to their other devices, and
 > yes of course others hated it.  The general hope among this group was that
 > it would become a user selectable behaviour setting through a
 > keyobard/trackpad applet in My Settings.   Alas, should I be informing the
 > deployed users not to get used to it, because it will be gone again in the
 > final 11-3? Or, does the AVC adjective limit this fix to a specific
 > architecture build?

it's not out of the question that this could be made user-selectable, but
there are no current plans to do so.

paul

 > 
 > Thanks
 > 
 > KG
 > 
 > 
 > 
 > > XO-1.75 RenderAccel disabled for increased graphics stability
 > > #11275 NORM 11.3.0: Add Browse 127 to the build
 > > #11078 NORM 11.3.0: minicom, lockdev and screen don't work after
 > > reboot due to rwtab tmpfs mounts
 > > #11097 Bump firefox and xulrunner to .20 versions (or the latest
 > > security update) (3.6.22)
 > > #11275 Add Browse 127 to the build
 > > #11214: migrate /boot/olpc.fth out of bootfw and into olpc-os-builder
 > >
 > > Changes and notes from os6:
 > >
 > > kernel:
 > > - AVC hack to disable tap to click
 > >
 > > Activity changes:
 > > -Browse-126
 > > +Browse-127
 > > _______________________________________________
 > > Devel mailing list
 > > Devel at lists.laptop.org
 > > http://lists.laptop.org/listinfo/devel
 > >
 > part 2     text/plain                 129
 > _______________________________________________
 > Devel mailing list
 > Devel at lists.laptop.org
 > http://lists.laptop.org/listinfo/devel

=---------------------
 paul fox, pgf at laptop.org