It does work, and many robots do so, but there are some bugs filed about cases where it does not work. For example: http://code.google.com/p/google-wave-resources/issues/list?can=2&q=setfield&colspec=Stars+ID+Type+Status+Priority+Milestone+Owner+Summary+Internal&cells=tiles <http://code.google.com/p/google-wave-resources/issues/list?can=2&q=setfield&colspec=Stars+ID+Type+Status+Priority+Milestone+Owner+Summary+Internal&cells=tiles>
On Mon, Nov 16, 2009 at 8:02 AM, Jacco <[email protected]> wrote: > I think currently communicating from robot to gadget is not possible? > > The gadget.setField does not change the state of the gadget in my > tests. > > Regards, Jacco > > On 12 nov, 16:48, just marvin <[email protected]> wrote: > > It occurs to me that since you'll need a bot and a gadget, you could > > just have the bot add the gadget(s) to the wave. Then you just need > > to add one thing to the wave and you'll know you have the correct > > environment for the gadgets. > > -- > > 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=. > > > -- 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=.
