You could have your edit form in a modal popup window. That would prevent
navigation until the popup form is closed/saved?
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf
Of Richard Rodseth
Sent: Thursday, 5 March 2009 10:50 a.m.
Thanks, but I'm specifically looking for an alternative to modal dialogs.
On Wed, Mar 4, 2009 at 2:33 PM, Wildbore, Brendon b.j.wildb...@massey.ac.nz
wrote:
You could have your edit form in a modal popup window. That would
prevent navigation until the popup form is closed/saved?
What i do is track user changes by setting some flags (plural because i need
to save bits of changes not everything on the form in one go). If the user
tries to get away from the tab/form, i stop the event and throw a confirm
alert box saying that there are changes that need to be saved. If he
So your basic approach is capturing all events elsewhere in the app, and
stopping them.
I was thinking along the lines of a navigationmanager which knows about a
current editing context, and could also be tied into deep linking support.
View state (selected tab, selected child of view stack)
I have not tried this, but if you are able to catch the hide event of the
'editing area' and cancel it,
it would be far easier to implement what you describe...I do not have access
to my builder at the moment
so i do not know if what i suggest is doable... Have a go if you like :-)
On Thu, Mar 5,
What i am doing at the moment sounds much like you are describing. My app
contains several window like components. Each one has an expand button. On
click a bubbling 'expand' event is dispatched. This in turn is caught in the
main app and processed in a 'expander' function. This checks for any
I do this by having all of my change or click or whatever events call a
single function that updates the model, and also sets a modified flag. The
flag variable, which is bindable controls the enabled property of my Save
button. I also can check it if my navigation permits the possibility of
7 matches
Mail list logo
