[GRASS-user] Freetype fonts in gis.m
Michael Barton
michael.barton at asu.edu
Sat Jun 10 01:44:53 EDT 2006
We don't restart d.mon gism for each layer, but d.font romans and d.frame -e
is run each time due to driver issues.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Sat, 10 Jun 2006 02:22:16 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: Hamish <hamish_nospam at yahoo.com>, <grassuser at grass.itc.it>
> Subject: Re: [GRASS-user] Freetype fonts in gis.m
>
>
> Michael Barton wrote:
>
>>> 2. gis.m provides no guarantees as to the order in which layers are
>>> rendered. If a command changes the font, whether other commands use
>>> the default font or the changed font depends upon the order in which
>>> the commands are executed.
>>
>> The layers are always rendered and composited in bottom to top order in
>> gis.m.
>>
>> Between each layer rendering, it is necessary to run a d.font command or no
>> text will render. Currently this defaults to d.font romans. It could be set
>> to a variable which, in turn, could be set by d.font.text or
>> d.font.freetype.
>
> You're still restarting the driver for every layer?
>
> Whilst inefficient, that does at least simplify the font issue.
>
> For now, it's simpler to keep the font handling entirely within gis.m,
> i.e. provide a user option to control the font used at startup
> (ideally, also provide an option to use freetype fonts).
>
> --
> Glynn Clements <glynn at gclements.plus.com>
More information about the grass-user
mailing list