But participants may want to be able to remove themselves. So my robot only re-adds two robots at the moment (that are needed for my application to function correctly).
On Jun 11, 8:41 am, Nathanael Abbotts <[email protected]> wrote: > One test you should include - check if the person removed themselves (for i > in event.participants_removed: if i != event.modified_by: add(i) ) > > On 10 June 2010 22:42, Anders <[email protected]> wrote: > > > I have written a robot that re-adds participants. It works really > > great! When one of the participants that gets re-added is removed by a > > user the robot instantly adds it back again. Within a fraction of a > > second. This hopefully solves the problem with keeping the waves > > public. An improvement would be to be able to set a filter so that my > > robot only gets called for those particular robots (only two at the > > moment) that I want to re-add. Because as it is now my robot of course > > gets called every time a participant is added or removed. That's a > > minor problem and will only become a larger problem if lots of people > > would use my application. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-wave-api%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
