On Mon, Mar 17, 2008 at 2:55 PM, Randy Kramer <[EMAIL PROTECTED]> wrote: > <quote> > I (Bert) needed other types of hooks, so I added more, which are now > integrated into the Patch Collection: > * modified_hook: called after the text buffer is modified > </quote> > > Does that hook tell what has been changed, or must one do things like compare > the textBuf before and after to see what has changed? No.
> > Also, you mention "identify more useful hooks" as one of the ToDos--I have > one > to propose (that would be useful if we (I) try to do the "Proof of Concept" > folding back end by simply having a document open in two places (more > description buried in the back end design document)). > > That woud be: > > * modified_rangeset_hook: which would be called after a rangeset is > modified (and it should report what has changed) the current hooks I use take no arguments, its only the 'event' that bothered me, not exactly what happened (like in the modified or cursor_moved events) Thats exactly what is needed to be done: identify hooks/events and the information what these should carry. > > There may be others that would be useful if: > > * I (or anyone else) pursues that "unusual" "Proof of Concept" approach > * if they are not already covered by the (textBuf) modified_hook > > For example, are changes in the selection(s) saved in the textBuf and > reported > in the modified_hook? > > How about changes in the scroll position of the document? hmm, a scroll_hook could open the door for a macro syncscoll feature, tony? Bert > > Randy Kramer -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
