Re: [patch] gl: do not force flush everytime uploading a glyph image to glyph cache

"Henry (Yu) Song - SISA" <[email protected]> writes:

> From fc3c82cf6a2dd706a97aea2b34c4ddd23eb6e939 Mon Sep 17 00:00:00 2001
> From: Henry Song <[email protected]>
> Date: Wed, 23 Jan 2013 11:55:44 -0800
> Subject: [PATCH] gl: add a force_flush flag in _cairo_gl_surface_draw_image.
>  In normal cases, we want to flush everytime we call this
>  function. But during uploading glyph to glyph cache, we
>  don't want to flush it everytime it uploads glyph images.

What are you using to ensure that flushes actually happen when updating
a piece of the glyph cache that has been used in the queued rendering?

The commit message could use some work.  The whole commit message is in
one line in the subject. Generally commit messages start with one short
line describing what the change is, that fits on an 80-character-wide
terminal when you look at it with "git show".  After that, start a new
paragraph that explains why.  An example update of your commit message
would be:

"
gl: Skip flushing queued rendering when adding a glyph to the cache.

We flush every time we change state that would change the result of the
drawing with the queued up vertices.  Typically when we call draw_image
on the current surface, we need to flush those verts because we don't
know what portion of the surface has been used in the queued drawing so
far.  But for adding glyphs to the cache, there is a a separate flush
when updating space in the cache that contains a used glyph, so we can
skip the flush in draw_image.
"

I have no idea if this is true or not, but it's an example of something
that would have explained to me why this change is expected to work.

-- 
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlEIY/AACgkQHUdvYGzw6vcclwCfU8xgGxJ1yvr8YuTWGhS4uuiD
NdkAn0YQA/KcmNHEfZebNXKb28qA+l2b
=x8ME
-----END PGP SIGNATURE-----