Yes, this actually seems to be a 'duplicate' (or another effect) of the same bug (3458952). As I already pointed out the activities should queued (and this was the fact before partial sharing...)
2012-05-23 10:17:39 PDT in Saros - Distribut...
donut87 committed revision 3932 to the Saros - Distributed Party Programming SVN repository, changing 1 files.
2012-04-01 00:45:46 PDT in Saros - Distribut...
donut87 committed revision 3926 to the Saros - Distributed Party Programming SVN repository, changing 1 files.
2012-03-31 10:07:45 PDT in Saros - Distribut...
This was ages ago ^^. I was just beginning to know Saros. I think we can reject my Feature request :-)
2012-03-25 06:38:05 PDT in Saros - Distribut...
donut87 committed revision 3883 to the Saros - Distributed Party Programming SVN repository, changing 14 files.
2012-03-25 02:18:59 PDT in Saros - Distribut...
It seems that these Activities are supposed to be queued (have a look at SarosSession.java lines 698 - 799), but something goes wrong. It was so much easier when we were sure that we eventually will have the whole project...
2012-02-01 17:01:17 PST in Saros - Distribut...
This is a more generell problem. The Question is: "What do we do, if Alice closes a file that was also edited by Bob?" If you think a little bit ahead it gets even worse... Imagine a file "A.java" is opened by Alice, Bob an both can write to the file. What if Alice and Bob did made changes to "A.java" and Alice decides to close without saving? What do we do? If we...
2012-02-01 15:15:14 PST in Saros - Distribut...