[Sugar-devel] Problem rejoining a shared Write

[Benjamin M. Schwartz]

J.M. Maurer wrote:
> While testing with salut, I now seem to be running into sugar bugs:
> 
> 1. Start an activity
> 2. Join the activity
> 3. Close the activity on the initiator side
> 4. Click on the activity from the donut on the initiator side to rejoin
> it

Could you clarify step 4?  Why didn't you go to the Neighborhood View to
rejoin?  Did you create a fresh instance or did you resume a saved instance?

> => This 'creates' a new activity instead of joining it, as
> self._shared_activity is not set to true.

Is it set to False?  self._shared_activity can take on many non-False values.

> It DOES however reconnect to
> the tube that was still there. This results in my case in having 2
> Writes on the same tube who both think they are in control.

It seems likely to me that this is a problem with Write being unable to
handle an instance that is both resuming from the datastore and joining an
existing shared session.  I know this is possible to handle, because
SharedTextDemo does it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : http://lists.sugarlabs.org/archive/sugar-devel/attachments/20090906/188897e3/attachment.pgp