[Google Wave APIs] Re: Should BLIP_SUBMITTED be fired when a gadget changes a state?

2009-11-17 Thread César Izurieta
If BLIP_SUBMITTED is still going to be fired, couldn't it have some event property to distinguish between events fired by a gadget state change and by a real blip submission? On Nov 12, 1:38 pm, cmdskp comdudes...@hotmail.com wrote: *and BLIP_SUBMITTED can still be used for both. On Nov 12,

[Google Wave APIs] Re: Should BLIP_SUBMITTED be fired when a gadget changes a state?

2009-11-12 Thread cmdskp
Ideally, I would like an event that only gets triggered on a text change. The reason being that my robot currently gets a lot of resubmitted blips because of a gadget in them being clicked on. They can contain a lot of text which is still the same and has been seen by the robot. This eats up

[Google Wave APIs] Re: Should BLIP_SUBMITTED be fired when a gadget changes a state?

2009-11-12 Thread cmdskp
*and BLIP_SUBMITTED can still be used for both. On Nov 12, 3:36 pm, cmdskp comdudes...@hotmail.com wrote: Ideally, I would like an event that only gets triggered on a text change. The reason being that my robot currently gets a lot of resubmitted blips because of a gadget in them being

[Google Wave APIs] Re: Should BLIP_SUBMITTED be fired when a gadget changes a state?

2009-11-11 Thread Austin Chau (Google employee)
Thanks for filing this. We will look into this. Austin On Wed, Nov 11, 2009 at 7:15 AM, César Izurieta cesar.izuri...@gmail.comwrote: I'm developing a robot that sends an email every time it receives a BLIP_SUBMITTED event. It all works just fine except when there are gadgets on the page