#6140 NORM Future : can start multiple activity instances by accident, and loose resumed edits (was: can start multiple activity instances by accident)

[Zarro Boogs per Child]

#6140: can start multiple activity instances by accident, and loose resumed edits
-------------------------------+--------------------------------------------
  Reporter:  AlbertCahalan     |       Owner:  tomeu                            
      Type:  defect            |      Status:  new                              
  Priority:  normal            |   Milestone:  Future Release                   
 Component:  journal-activity  |     Version:  Development build as of this date
Resolution:                    |    Keywords:                                   
  Verified:  0                 |    Blocking:                                   
 Blockedby:                    |  
-------------------------------+--------------------------------------------
Changes (by garycmartin):

  * owner:  jg => tomeu
  * version:  => Development build as of this date
  * component:  distro => journal-activity


Comment:

 This is a little more severe than I first thought.

 Testing with Update.1 690, an accidental double click in the Journal (v83)
 entry icon or the resume button will try to launch 2 instances of the
 activity accessing the same data. One of them will usually hang and sit
 pulsing in the home view (eating cpu). The other will usually start-up and
 display the resumed data. Any changes made to the resumed data will
 usually be lost, presumably as the other activity has it's hooks into the
 object data it'll end up reverting the data store to the old state (say
 when it finally quits when you reboot). Tested in both Write (v54) and
 Paint (v18) activity.

 The Journal should really prevent duplicate launches of the same data
 object to avoid this condition.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6140#comment:2>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system