#2159 NORM Trial-3: Journal should be the active activity at boot

[Zarro Boogs per Child]

#2159: Journal should be the active activity at boot
---------------------+------------------------------------------------------
  Reporter:  Eben    |       Owner:  marco  
      Type:  defect  |      Status:  new    
  Priority:  normal  |   Milestone:  Trial-3
 Component:  sugar   |     Version:         
Resolution:          |    Keywords:         
  Verified:  0       |  
---------------------+------------------------------------------------------
Changes (by danw):

 * cc: danw (added)

Comment:

 OK, so the problem is that the Journal starts itself up iconified, so as
 to not steal focus from the shell, and it would be difficult to change
 that. So here's what I did:

 (1) When a new activity appears and there is no _current_activity,
 HomeModel now makes that activity the _current_activity, even if it
 doesn't have any visible windows. (This means the Journal now properly
 becomes the _current_activity at startup.) (HomeModel also now makes sure
 to figure out what the new _current_activity should be after you close the
 previous one, so that the activity donut can highlight the right wedge;
 previously, after you quit an activity, the donut would show no
 highlight.)

 (2) Shell.set_zoom_level() now calls present() on the current ActivityHost
 when switching to Activity view. (Which in the journal's case will force
 it to deiconify.)

 (3) ActivityHost.present() no longer calls gtk.get_current_event_time(),
 because (a) if the code was invoked via the F4/Activity key, then there is
 no "current event" because SugarKeyGrabber happens outside the gtk main
 loop, so get_current_event_time() will return 0; (b) libwnck will g_warn
 if you pass 0 for the timestamp; (c) matchbox doesn't even look at the
 timestamp you pass anyway. So we just always pass "1" now.

 Marco?

-- 
Ticket URL: <http://dev.laptop.org/ticket/2159#comment:1>
One Laptop Per Child <http://laptop.org/>