Re: EditingContext question
Re: EditingContext question
- Subject: Re: EditingContext question
- From: Jonathan Rochkind <email@hidden>
- Date: Thu, 15 Apr 2004 10:19:23 -0500
If you have given the user a seperate editing context for that new
window---then it doesn't really matter if you leave it lying around
with unsaved changes, since it was a seperate editing context that
you will not use again. Right?
At any rate, that is a description of how I handle such things.
Create a new seperate editing context for a particular edit
window---if they save, then of course saveChanges(). If they just
abandon the window, no skin off my back, I do nothing, just leave
that editing context with unsaved changes that will in fact never be
saved.
That certainly isn't the only way to handle this, but it's what I do.
--Jonathan
At 9:00 PM -0500 4/14/04, James Cicenia wrote:
Hello -
I want to know what is the best way to handle "open" editing contexts?
In other words, I have a user launch a window with a different editing
context to edit the specific object. Now, when I spawn this window I
create the new object, insert it into the editing context, initialize and then
pass it to the nextPage which in this case is a popup.
How do I handle the person closing the window and not using my cancel?
This new object will still be in the editingcontext which is session based.
Should I just call a "revert" before launching any of my windows?
thanks again,
James Cicenia
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.