Hi Thomas, thanks for the detailed explanation. I added a window closing
handler but I then have the issue of handling mayStop clean up, ie mayStop
seems to be called first and does the cleanup, in which case if the user
decides to cancel the leave of the activity, the activity is in a cleaned
OK, it looks like I might have managed two birds with one stone.
Basically I have a leave flag that I set to true at the creation of the
activity. This flag is set to false if there is a PlaceRequestEvent and the
new place is not null. In mayStop I first save my workspace and then I
check the
mm I must come back on what I said... It turns out the PlaceRequestHandler
is called after the mayStop (actually during which is plain weird), or at
least after the check is done in mayStop, so too late anyway... Is that
normal? I have only tested in dev mode and with gwt 2.4.
So I tried
me again... last one I promise.
I ended up using PlaceChangeEventRequest only. The place returned by
getNextPlace is not null actually. What I ended up doing is have all my
places implement my ow place interface and check if the getNextPlace is of
that type. If not, it means we are leaving the
On Tuesday, July 3, 2012 6:20:09 PM UTC+2, Thomas Lefort wrote:
me again... last one I promise.
I ended up using PlaceChangeEventRequest only. The place returned by
getNextPlace is not null actually.
Ah yes sorry; I haven't check but from memory it should/could/might be a
Place.NOWHERE.
Hi,
I was relying on mayStop to save my user's project when they leave the
activity but it seems to work in some cases only, ie when navigating from
one activity to another but not when leaving the application or closing the
browser... I don't know if it is normal? may be there is not enough
On Monday, July 2, 2012 9:31:56 AM UTC+2, Thomas Lefort wrote:
Hi,
I was relying on mayStop to save my user's project when they leave the
activity but it seems to work in some cases only, ie when navigating from
one activity to another but not when leaving the application or closing the
