Submitted by David_H on 2016/01/08 16:49
Or some form of one?
 
Thanks

Comments

Hi David,
 
Databases don't typically have trash cans... but... other than some probably minor performance issues, I don't see why it could not be implemented.
 
That and multiple undos are 2 things I'd like to add on the usability front
 
HTH !
 
Pierre_Admin
 
 

WayneK

2016/01/14 11:28

In reply to by Pierre_Admin

Pierre,
 
I think an undo that works in all circumstances is one of the best features your could add.  Multiple undo's would be great but just one that works all the time would be a huge improvement.  I've never gotten undo to work at all for me.
 
Maybe the biggest benefit is reducing frustration for someone learning the program and running into the "what just happened?" situation that naturally occurs. 
 
 
Wayne
 

viking

2017/04/12 00:28

In reply to by WayneK

Are there approximate ETAs on:
One-step Undo?
Multi-step Undo?

Pierre_Admin

2017/04/12 00:57

In reply to by viking

There is already field-value change / delete undo. Missing is parent change / delete and item delete undo. 
 
Let me finish the Calendar (and Google Calendar sync) and I'll then look at it. 
 
Pierre_Admin
IQ Designer
 

viking

2017/04/12 16:32

In reply to by Pierre_Admin

[quote=Pierre_Admin]
There is already field-value change / delete undo. Missing is parent change / delete and item delete undo. 
 
Let me finish the Calendar (and Google Calendar sync) and I'll then look at it. 
 
Pierre_Admin
IQ Designer
 
[/quote]
After I move an item to a different parent; it can't be undone. Maybe that is the same as "parent change"?
After I link an item to a new parent (ctrl-drag-drop), in another grid and hit ctrl-z, the item is still there but the item text is deleted.
Same if I move [drag-drop] an item to a different grid, so that it exists in 2 grids; ctrl-z just deletes the item text.