#10396 NORM 10.1.3: Read must focus in the view if XO is post in ebook position
Zarro Boogs per Child
bugtracker at laptop.org
Mon Oct 18 14:56:45 EDT 2010
#10396: Read must focus in the view if XO is post in ebook position
-------------------------------------+--------------------------------------
Reporter: godiard | Owner: godiard
Type: enhancement | Status: new
Priority: normal | Milestone: 10.1.3
Component: read-activity | Version: Development build as of this date
Resolution: | Keywords:
Next_action: review | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-------------------------------------+--------------------------------------
Comment(by pgf):
this ticket was starting to confuse me, so i just looked at and tried Read
to see how it works.
Read already has some key actions that it performs regardless of focus --
it will zoom in or out if you use the "check" or "square" gamepad keys.
the latter actions (presumably -- i'm no python expert) happen because the
KP_Home and KP_End keynames are handled in
ReadActivity._key_press_event_cb(), and cause zoom_in/_out() routines to
be called.
it seems to me that the d-pad keys could be similarly bound in a focus
independent way by having the same routine look for KP_Up, KP_Down,
KP_Left, and KP_Right. this will catch just the d-pad keys, and not the
"regular" arrow keys, and of course they should somehow be bound to
scrolling operations.
my assumption is that there is no reason that the d-pad keys should ever
be used for field or tab selection -- i.e., the regular arrow keys would
probably be used for that. so it's okay for the d-pad keys to always
scroll, no matter what the focus, and, more importantly for this ticket,
no matter whether the laptop is in ebook mode or not.
(disclaimer: i'm looking at the code for Read-86)
--
Ticket URL: <http://dev.laptop.org/ticket/10396#comment:17>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list