Robert Roessler wrote:
Are you profiling the first instance created? You might be measuring
the initial pango (the gtk text rendering engine) initialization.
Subsequent calls to pango will hopefully be faster.
Thanks, but unfortunately (that would be too easy), this call stabilizes
at 0.08 - 0.10 secs (I did not post this level of detail because it was
already getting too wordy)... so while the Pango rendering machinery
seems to be on the heavyweight side, I wonder why this particular call
(SCI_TEXTWIDTH) is so expensive?
A possibility is that the style data refresh accounts for some of the
time, though I wouldn't of thought it would be very much.
In case anyone is about to ask, I have left the "buffered draw" and "two
phase draw" settings alone, and they are documented as defaulting to true.
I doubt they have any effect on measurement speed.
The good news is that I am sure that things will get faster as GTK
transitions to Pango on the Cairo backend... ;)
I think cairo performance is likely to be a mixed bag -- more important
here is the performance work being done on pango. I haven't tried the
newer versions, but they are looking to optimize the common cases.
John
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
