Openmoko Bug #1549: [exposure] want to launch exposure again while it is in the e-illume bar, need 5~10 sec

[Openmoko Public Trac]

#1549: [exposure] want to launch exposure again while it is in the e-illume bar,
need 5~10 sec
------------------------+---------------------------------------------------
 Reporter:  wendy_hung  |        Owner:  marek   
     Type:  defect      |       Status:  assigned
 Priority:  normal      |    Milestone:  ASU     
Component:  E - Illume  |      Version:          
 Severity:  normal      |   Resolution:          
 Keywords:  must have   |     Blocking:          
Blockedby:              |  
------------------------+---------------------------------------------------

Comment(by raster):

 ok 1. bar is not relevant to any changes in exposure. it is entirely done
 inside the window manager. for me here, it works 100% of the time, no lag.
 the problem may be that when u press, u press AND drag (a little) and that
 is not counted as a press (as that list is actually scrollable... so if
 it's long enough...) i can change the sensitivity to allow more drag to
 still be registered as a click. but other than that. so if you click on
 home or exposure and the top bar doesnt slide back on its own - it decided
 you clicked and DRAGGED and thus didnt want to select it - that may be
 what you see.if you use a fingernail or stylus its always accurate - with
 the "pad" of your finger - it wiggles about a lot when u press
 something... that's why i provided config values fortuning it. try this:
 click the wrench/spanner to get illume's config (thank god i haven't
 removed it!) and then in finger scrolling select "Very Low" and see if
 things improve for you :)

 anyway - for the bar, there is not 1 thing you can do to exposure to
 affect it in any way as exposure isnot involved except in drawing itself
 when its window is shown.

 2. launcher - sigusr2... did u set up a sgnal handler? or are you using
 ecore's sigusr -> event conversion wrapper? (and you may have no idea
 because python has hidden it from you...).
 normally signals are never delayed in linux... well - not by 10 seconds.
 so its something in the handler later...

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1549#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac