Randall R Schulz <[EMAIL PROTECTED]> さんは書きました:
> On Tuesday 14 November 2006 13:11, Mike FABIAN wrote:
>> ...
>> > So my question is this: Is this a bug or is there some kind of
>> > asynchronous rendering of smoothed fonts that sometimes leads to a
>> > ragged font display upon first use of a given font but which is
>> > later replaced with the smoothed version, once the smoothed glyphs
>> > have been rendered?
>>
>> This might be the following bug:
>>
>> http://bugzilla.novell.com/show_bug.cgi?id=193095
>
> There doesn't appear to be any mention in that bug report of spontaneous
> replacement of the raggedly rendered glyphs with smoothed ones shortly
> after the original, ragged display.
The bug report does mention this, see for example comment #23
Comment #23 From Felix Möller 2006-11-10 16:35:53 MST
i just ran gnome-theme-manager as was said in 214280. This
crashedfirefox and thunderbird. But now all font problems are gone!
So just starting gnome-theme-manager and exiting it without doing
anything solves this problem.
Federico Mena Quintero recently explained me that GNOME works as
follows:
- The GNOME control center sets some GConf keys.
- The running gnome-settings-daemon gets notified about changes in the
GConf keys, and it does the following. First, it sets some X
resources.
Second, it uses the XSETTINGS protocol to tell GTK+ apps to refresh
themselves.
- Running GTK+ apps pick up the XSETTINGS notification, call
cairo_set_font_options(), and redraw their widgets.
You can try that out by starting for example gedit and then
gnome-font-properties and change the anti-alias setting in
gnome-font-properties. You will see that it applies to gedit
immediately.
I am not sure which GNOME programs apart from gnome-font-properties
and gnome-theme-manager can trigger this process to make GTK+ apps to
refresh themselves according to the current settings of the Xft.*
resources. But probably there are others.
Therefore I guess that some gnome thing started and triggered this
process while you were trying to make the snapshot of Beagle (which is
a GTK+ program).
> I assume rendered glyphs are cached (lest font rendering consume
> inordinate CPU cycles throughout the system's operation).
>
> To your knowledge, is there any code that might account for ragged
> (point-resampled) glyphs being used (transiently) when the smoothed
> ones are not available on a timely basis?
No.
--
Mike FABIAN <[EMAIL PROTECTED]> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
