Quoting Bert Wesarg <[EMAIL PROTECTED]>: > On Mon, Mar 17, 2008 at 9:30 PM, Randy Kramer <[EMAIL PROTECTED]> wrote:
> > Starting a small list: > > > > * modified_hook--modify it to report what has changed in the textBuf > should this be fired before or after the change happen? so, should it > report what will happen, or what happened? If there's a modification, you should be able to pick it up from undo information. This implies that at least one level of undo information should be available at all times, even when the undo function is turned off. Accessing undo information could be useful in many areas (particularly type-in and word completion macros). > > * modified_rangeset_hook--should report the change(s) (additions, > > deletions, locations) Support for storing rangeset info in the undo list? Hmm best avoided. However, it would be great to allow dragging of rangesetted text which wouldn't wipe out intermediate ranges. > > * cursor_moved event--should report the change (i.e., the new > > location) > because this is fired after the actual movement, you get the new > position easily with the $cursor variable. so it maybe has more value > if the old position is given, or this is fired before the movement > happen > > > * selection_change hook--should report the new selections > > * scroll_change hook--should report the new scroll position (is that > the > > top line (or the first character) in the display?) > > you see, there are more questions you must think of for each hook, not > just a oneliner Tony -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
