@Daniel Faust gadgets.util.registerOnLoadHandler is to do with the gadget. I explained how it works. The nature of it has changed apparently, the call used to be stuffed in the onload attribute, now it is directly after where your code is placed but not after everything. This has caused some problems with older gadgets, allegedly.
@qMax I see what you mean now, but when you were outputting to the console I didn’t see null, which might be due to a small delay. Yes it needs to find the state which is a product of a wave and gadget instance in the wave. If it is not aware of that that then its 'state' is non persistent. You can easily see this by opening the frame in a new tab. There simply is no shared state. As to whether it is by design, well you could consider it a design limitation I guess. -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=.
