1. glpyph caching,
Doesn't the cache work automatically for any used font size?
per font size instance there is a glyph cache - BUT now i'd
need to handle per
size AND transform (scale h AND v). i'd either need a glyph
cache per one of
these or change the glyph hash key to
On 14.09.2004 14:13:45, Nemec, Bernhard wrote:
1. glpyph caching,
Doesn't the cache work automatically for any used font size?
It might, but you have to generate it each ever time you want it at a
new scale. You got CPU and Memory loss...
Julien
On Tue, 14 Sep 2004 14:13:45 +0200 "Nemec, Bernhard"
(B[EMAIL PROTECTED] babbled:
(B
(B 1. glpyph caching,
(B
(B Doesn't the cache work automatically for any used font size?
(B
(Bper font size instance there is a glyph cache - BUT now i'd need to handle per
(Bsize AND transform (scale h
On Wed, 15 Sep 2004 09:08:51 +0900 Carsten Haitzler (The Rasterman)
writes:
On Tue, 14 Sep 2004 14:13:45 +0200 Nemec, Bernhard babbled:
1. glpyph caching,
Doesn't the cache work automatically for any used font size?
per font size instance there is a glyph cache - BUT now i'd need
Hi,
looking at evas_engine_*_font_draw(), I wonder why we render the font first
and scale the result afterwards.
Shouldn't we render the font in the target size directly, in order to
avoid loss of resolution?
Thanks,
Bernhard
---
This SF.Net
On Mon, 13 Sep 2004 14:53:43 +0200 "Nemec, Bernhard"
(B[EMAIL PROTECTED] babbled:
(B
(B Hi,
(B
(B looking at evas_engine_*_font_draw(), I wonder why we render the font first
(B and scale the result afterwards.
(B Shouldn't we render the font in the "target size" directly, in order to
(B
