Undoing JUST the a row delete

[Mike Fox]

I am trying to implement undo in an application. The problem is the user wants a granular undo like word or studio.

Here's the issue:
1. Bring up a record, and edit a field.
2. move to a new field and edit
3. delete the record
4. Now hit undo.

If I "undo" the delete using datarow.undo() or datarow.rejectc hanges(), it reverts to the original state and I lose the changes fromstep 1 and 2. The user wants to be able to undo JUST the delete, and then udo the field changes with subsequent undo's if desired.

All I really want to do is set the row from rowstate=delete d back to rowstate=modifi ed or unchanged. .net 2 has a setadded and setmodified, but these only work on rowstate=unchan ged.

Anybody have any ideas how to handle this?

From http://www.developmentnow.com/g/36_0...ges-csharp.htm

Posted via DevelopmentNow. com Groups
http://www.developmentnow.com

[Joanna Carter [TeamB]]

"Mike Fox" <no****@develop mentnow.com> a écrit dans le message de news:
f9************* *************** **... icrosoft.com...

|I am trying to implement undo in an application. The problem is the user
wants a granular undo like word or studio.
|
| Here's the issue:
| 1. Bring up a record, and edit a field.
| 2. move to a new field and edit
| 3. delete the record
| 4. Now hit undo.
|
| If I "undo" the delete using datarow.undo() or datarow.rejectc hanges(), it
reverts to the original state and I lose the changes fromstep 1 and 2. The
user wants to be able to undo JUST the delete, and then udo the field
changes with subsequent undo's if desired.
|
| All I really want to do is set the row from rowstate=delete d back to
rowstate=modifi ed or unchanged. .net 2 has a setadded and setmodified, but
these only work on rowstate=unchan ged.

Add the row to your own "deleted" list when marking it as deleted, and then
remove it after restoring the state back to modified.

Joanna

--
Joanna Carter [TeamB]
Consultant Software Engineer

[animus.blue]

I implimented an undo function into one of my application by creating a
LIFO (last in, first out) collection of changes. You could store the
type of change it was (adding, removing, editing, etc), the unmodified
data ( like your datarow ), and then where the row was located. When
the user hits the 'undo' button you could call a function that take the
newest item from your undo collection and uses the information to undo
that change. This way the user could hit the Undo button multiple
times. Say your user wants to undo the edit he made right before
deleting that row; he could hit the 'undo' button twice and undo both
the delete and the edit. Just make sure you remove the undone item from
your collection or you'll end up undoing the same thing over and over.

This is just my two cents, though. :)