From: "Sammy Mitchell" 
@Date: Wed, 22 Jan 2003 14:41:48 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



Bill Stewart said:
>A corresponding neat idea would be to hop back to the last
>changed line in the buffer.
>
>Also neat would be a visual indicator of changed lines in
>the buffer.

I've been ciphering on how I might implement these.  They
seem like basically the same problem internally.

How does this sound:

Allocate a 32-bit integer (called line_change_count) for
each line.

Whenever that line is changed, increment line_change_count.
This should be done in the same code that builds the undo
list.

Whenever undo is performed, decrement the line_change_count
as appropriate.

Whenever redo is performed, increment line_change_count as
appropriate.

(I'm assuming that no one will ever make 2**32 changes to a
single line?  I wonder how long it would take to make that
many simple changes to a single line?)

I think this will work?

But please don't ask to show where the change starts/stops
on each line!

--
Sammy Mitchell

--
TSEPro mailing list



---
[sawasdi.apana.org.au] (3:800/846.13)