Using the back/forward buttons for undo/redo is not a good idea. There are too many ways that your client app and server state could get out of sync. The forward/back button and history management should be used to control view state rather than application data state.
This came up during the Q/A part of one of the Google I/O 2009 presentations (around 49:33): http://code.google.com/events/io/2009/sessions/EffectiveGwt.html They put a button on the UI that is explicitly labeled "Undo" to make it clear that that's how to undo application data state changes. My guess is that you should be able to retrofit your existing database state management to be triggered by undo/redo buttons instead of history change events. You should check out the whole presentation to understand what they say about how the back button behaves in their application, and for other generally useful tips. -Brian On Oct 7, 6:40 am, vokke <[email protected]> wrote: > Hello Newsgroup, > > I try to keep my database in the right state using the HistoryHandler > or the deprecated HistoryListener. > It's kind of undo/redo-function. > My problem is, if you press the back or forward-button very quickly > (doubleclick), it seems that the HistoryHandler does not get all the > events, so my database gets out of sync. > Is there any help? > > Best regards, > Vokke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
