Neil Hodgson wrote:
Robert Roessler:
While all of this is semi-believable, this does not seem to be what is
happening...
Eh? My message was replying to Armel's about display update transactions. The relevant post to your issue was the one about GtkRange.
I thought it was all about me - er, my issue... taken in the generic "classic area update issues in graphics systems" sense, then it is true, my post did not contribute much. :)
I wanted a way of telling when you are at the "end" of an Undo/Redo
sequence, so that calling SetScrollBars could be deferred until
then... ...
It appears to work fine, but I look forward to hearing from Neil that
a) this will work,
It may work. I haven't been able to think of a good reason why it wouldn't.
Nor I - but then, your opinion on this subject is more informed.
or b) "X" is why he wasn't using this flag.
It wasn't added for that purpose.
Like I said, I assume you would know... but, might you now be willing to see SC_LASTSTEPINUNDOREDO in the larger context of "which operations that do not change buffer (text OR style) contents could be reasonably deferred until the end of this undo sequence?" There may be more candidates for this type of platform-independent optimization.
While I realize that the case that was giving me so much trouble might not intersect much with the needs of a more-or-less straight-up text editor like SciTE, the larger undo/redo batching *could* happen in pretty much any custom use of Scintilla as an editing component.
My 0.02 USD - or should that be 0.0258012 AUD? :)
If you want me to make a real patch for this, I will even comment it.
Robert Roessler [EMAIL PROTECTED] http://www.rftp.com _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
