[Bugs] #2367 UNSP: [Dextrose 2] Secondary palette appears too soon on Neighborhood view buddy icons

[Sugar Labs Bugs]

#2367: [Dextrose 2] Secondary palette appears too soon on Neighborhood view buddy
icons
------------------------------------------+---------------------------------
    Reporter:  FGrose                     |          Owner:  bernie                     
        Type:  defect                     |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  Dextrose                   |        Version:  Unspecified                
    Severity:  Unspecified                |       Keywords:  design                     
Distribution:  Dextrose                   |   Status_field:  Unconfirmed                
------------------------------------------+---------------------------------

Comment(by FGrose):

 I've done some testing with Dextrose 2 build 1dx2 Dextrose 2 International
 running on an XO-1 and with Sugar 0.89.10 in a Xephr window on Fedora 14
 beta (kernel 2.6.35.4-28.fc14.x86_64) in an 3.2-GHz, 3.3-GByte RAM
 workstation.

 I tried these settings:

 (in palettewindow.py)  0.0 to 0.6 seconds
 {{{
 self._popdown_anim = animator.Animator(0.6, 10)
 }}}

 The behavior varies with the processor and environment.

 There is sufficient delay in system overhead for the primary palette
 popup,
 {{{
 self._popup_anim = animator.Animator(0.0, 10)
 }}}
 to use the 0.0 second delay and still allow one to move the mouse pointer
 casually over buddies or access points without revealing the name for
 every target annoyingly.

 The popdown delay of 0.6 second allows one to hover a target, reveal just
 the name, and then move the pointer away, and still have sufficient time
 to read the name.  (Setting this popdown delay to 0.0 second as proposed
 in http://bugs.sugarlabs.org/attachment/ticket/1169/0001-Reduction-in-the-
 time-taken-for-loading-of-the-menu-.2.patch (ticket #1169) is too short to
 comfortably read the name before the palette is dismissed.)

 I tried these settings:
 (in palette.py)  0.0 to 1.0 seconds
 {{{
 self._secondary_anim = animator.Animator(1.0, 10)
 }}}

 Here the different processors and environments had a greater effect.

 On the XO-1 the secondary palette could be delayed only 0.6 second and
 usually one could move the pointer away from the target to avoid showing
 the secondary palette, but in the Xephyr window, delays less than 1.0
 second would usually cause the secondary palette to be revealed briefly,
 and distractingly.

 In summary,
 {{{
 self._popup_anim = animator.Animator(0.0, 10)
 self._popdown_anim = animator.Animator(0.6, 10)

 self._secondary_anim = animator.Animator(1.0, 10)
 }}}
 are the settings I would recommend based on these tests.

 The 1.0 second delay for the secondary palette popup is beyond the 0.5
 second limit that was suggested, but does help with discoverability (as
 suggested in ticket #1169), and avoids the surplus exposure of information
 for the Neighborhood view use case.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/2367#comment:3>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system