Hi everyone, I just noticed something which is the result of poor usage of the Wave app (on my part), not necessarily any design flaw in the program itself...but still may affect the app's overall usability from a developmental standpoint. Naturally, the intended firing of the BLIP_SUBMITTED event is the point at which a user clicks the Done button in a blip or hits Shift+Enter...but BLIP_SUBMITTED event occurs for that user when she for whatever reason clicks out of the wavelet (i.e., selecting another wave from the user's Inbox pane).
Obviously, this is trivial in situations where a robot echoes input, but might be more problematic in cases of running a CRUD operation or modifying user profile info. Is there a known way we as Wave API developers can program defensively against this "accidental event"? Thoughts? Jason :) [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
