CLI undo edit?

[Neil Williams]

On Thursday 25 August 2005 9:21 pm, Derek Atkins wrote:
> Do you really need to keep track of the operations individually?

Not particularly, it just seemed handy to use an enum initially - I was 
thinking that a switch() statement was going to be needed later. I was 
planning to differentiate a MODIFY from a CREATE but I think that was just a 
hangover from tying the undo idea to events and dirty instances.

> I would think a much better API would be:
>   QofOperation qof_book_start_operation(QofBook* book, const char
> *op_name); void qof_book_end_operation(QofOperation oper);

Makes sense.

> At least that's my take on it all.

What about the number of undo operations to hold relative to the number of 
changes per operation?

It's not a problem for the CLI implementation, it's more for the future.

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20050825/dd4e9e8a/attachment.bin