root blips stay in un-submitted mode after robot adds content

0 views
Skip to first unread message

Monika Adamczyk

unread,
Aug 18, 2009, 9:24:03 AM8/18/09
to Google Wave API
Anybody knows why root blip requires explicit click on 'Done' button
via UI after robot updates its content (either via
Blip.TextView.append or replace method? I have observed the same
behavior in a wave that includes my own robot as well in one that has
robot (Polly the Polster) written by Google folks . This is not the
case with other blips. All blips but root are in submitted state.
I checked the robot API and I do not see a method that would allow me
to do it and in my opinion this is a bug (or at least a feature that
is missing).

Monika

Rob Weaver

unread,
Aug 19, 2009, 11:01:47 AM8/19/09
to Google Wave API
I don't see that behavior on the carrides robot and it posts to the
root wave.

Definitely sounds like a bug of some sort to me.

Monika Adamczyk

unread,
Aug 24, 2009, 8:53:29 AM8/24/09
to Google Wave API
Is the robot written in Java or python and can you give me the address
of the robot so I can see the difference?

Monika


On Aug 19, 11:01 am, Rob Weaver <webwe...@gmail.com> wrote:
> I don't see that behavior on the carrides robot and it posts to therootwave.
>
> Definitely sounds like a bug of some sort to me.
>
> On Aug 18, 6:24 am, Monika Adamczyk <moni...@gmail.com> wrote:
>
> > Anybody knows whyrootbliprequires explicit click on 'Done' button
> > via UI after robot updates its content (either via
> >Blip.TextView.append or replace method? I have observed the same
> > behavior in a wave that includes my own robot as well in one that has
> > robot (Polly the Polster) written by Google folks . This is not the
> > case with other blips. All blips butrootare in submitted state.
Reply all
Reply to author
Forward
0 new messages