check if you use Require feature="wave-preview" recently it is known to break getState() in Chrome.
On 10 дек, 05:50, dirtside <[email protected]> wrote: > I'm developing a Wave gadget. It sets a callback function for > setStateCallback() and setParticipantCallback(), which apparently gets > called immediately, three times (I'm guessing once for the > setStateCallback and once each for the two participants). > > The callback function (updateDisplay) calls another internal function > which calls wave.getState(). Well, the first time it calls > wave.getState() I get a JS error saying that wave.getState() is null, > which I guess means it hasn't been initialized yet. So my question is, > why is wave calling the callbacks before the wave object is fully > initialized, or am I doing something wrong? -- 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.
