Neil Hodgson wrote:
Robert:
Next, I tried to use SCN_MODIFYATTEMPTRO notifications to remove the indicators... ultimately, this does not work out either, since Undo does NOT trigger this notification! :(
Mark Hammond implemented this notification so that he could check the file out of source code control when the user tried to edit it. Thus the file was expected to start out in read-only mode so undo would not be relevant.
I believe this to be fixable, and am willing to do so... does anyone see a problem with issuing this notification (attempting to Undo/Redo with a doc that is AT THAT TIME set read-only)? All I am proposing is just issuing the expected "NO" when trying to do something that already is being blocked anyway.
It should be OK.
BTW, in case my "Undo/Redo" performance thread did not make it clear, this code is "completed" / ready for NH review. It does exactly what *I* need, BTW. :)
The key is having the ability to get a notification about changing the doc AND be able to change STYLE information while processing it - which is beyond what the the [much more detailed] SCN_MODIFIED supports...
It is currently available in
http://www.rftp.com/lazyplus.zip
BUT note that it is combined with the Undo/Redo stuff. If you really feel you need to evaluate this one by itself, let me know... and I will look into splitting the two "patches".
Robert Roessler [EMAIL PROTECTED] http://www.rftp.com _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
