On 25/10/14 01:48, Tudor Girba wrote:
Hi Steph,
No. It's just a stupid dump on the harddisk of the current contents as
soon as there is a change. Where do I find more about the undo mechanism?
Look in the history package in the image
A HistoryIterator holds an UndoRedoGroup in order to store an history of
commands with the possibility of undoing and redoing. The iterator
cursor is represented by the index inst var. Index always contains the
position of the command that can be currently undone. So, undo decrease
index and redo increase index. When a new record is stored, then, index
contains the newly added record position.
See HistoryIteratorTest for examples.
Cheers,
Doru
On Sat, Oct 25, 2014 at 8:40 AM, stepharo <[email protected]
<mailto:[email protected]>> wrote:
For Instant caching did you use the undo mechanism of Alain?
Stef
On 25/10/14 06:19, Tudor Girba wrote:
Hi,
We are quite actively working on GT.
First of all, thanks everyone for the feedback. We take it quite
seriously and we do our best to take it into account. Please keep
the discussions flowing.
I summarized some of the things that happened recently in the
playground and inspector here:
http://www.humane-assessment.com/blog/gt-developments-endless-playground-memory-sharing-and-others/
Let us know what you think.
Cheers,
Doru
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
