Robert Roessler: > Nope, I do not care about handles (or the "duplicate markers on line" > case)... the no-notification thing (as a low-level "under the radar" > approach) seems to fit the way I see this being used. It is true that > the notifications can be turned-off or ignored, much like the whole > thing can be simulated by interpreting the bits yourself and doing > multiple SCI_MARKERADD calls - it just seemed a logical grouping of > macro-operations to bundle.
I'm more in favour of allowing users to compose operations out of simple actions rather than trying to predict which things they will want to do together. > So, if you will not go for a "no-notification" version of this, are > you disposed to accept a "well-written etc" implementation of > SCI_MARKERADDSET? OK. I'd be happier if you found out what your actual problem is. It shouldn't be speed of switching event masks which is a very simple operation. There could be unwanted processing occuring within NotifyModified but it should be possible to work out how to fix that. > If I need to preserve the notification behavior, I > trust that *one* NotifyModify call will suffice for both the > [optional] notification and the RedrawSelMargin? Yes. Neil _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
