nanogui: request for font utilities


Previous by date: 6 May 1999 20:12:24 -0000 Re: request for font utilities, Greg Haerr
Next by date: 6 May 1999 20:12:24 -0000 Developers, klindsay
Previous in thread: 6 May 1999 20:12:24 -0000 Re: request for font utilities, Greg Haerr
Next in thread: 6 May 1999 20:12:24 -0000 Re: request for font utilities, Ben Pfaff

Subject: Re: request for font utilities
From: Ben Pfaff ####@####.####
Date: 6 May 1999 20:12:24 -0000
Message-Id: <87n1zi6jrq.fsf@pfaffben.user.msu.edu>

Greg Haerr ####@####.#### writes:

[...]
   So - bogl definitely should handle reading in .bdf fonts.  The architecture should
   work with the same bogl_font struct whether the font is compiled-in or read in, 
   and there should be a compile-time option.  This means that you should "name" the
   compiled in fonts, and let the mid level ask for fonts by name, and they will either get the
   "fast" (compiled-in) or slower disk read in font or NULL depending on the compile time options.
[...]

Yes, I will work on that.  Probably some working code later today or
this weekend maybe.

   BTW - you have a bug in the *_pointer routine in all your bogl libs.  The bogl_pointer
   routine reads a cursor from struct bogl_pointer, which uses ->hx and ->hy members.
   These are adjusted in the first line in the proc:

	   x1 -= pointer->hx

   The hotspot adjustment code is bad because arrow.c lists a -1 offset for the 
   hotspot on the mouse cursor.  This needs to be changed to not adjust for -1 hotspots,
   or, preferably, 0,0 be used to indicate the actual cursor hotspot, which is what I did.

Here, let me explain the rationale behind the cursor hotspot: the
hotspot is the point at which the user expects the pointer is
pointing.  For the standard arrow cursor, this is the pixel directly
to the upper-left of the arrow itself; i.e., it's not actually part of
the bitmap.  This is intentional.

The reason that the position of the cursor is adjusted for the hotspot
position is so that when the cursor type changes, the cursor won't be
pointing to a different spot on the screen.  i.e., if you change from
an arrow cursor to an I-beam for text, then the I-beam will be
centered over the place where the arrow was just pointing to.

   Now that I have full blown cursor clipping and line drawing working, I'm finding
   a number of off-by-one bugs.
-- 
"To the engineer, the world is a toy box full of sub-optimized and
 feature-poor toys." --Scott Adams

Previous by date: 6 May 1999 20:12:24 -0000 Re: request for font utilities, Greg Haerr
Next by date: 6 May 1999 20:12:24 -0000 Developers, klindsay
Previous in thread: 6 May 1999 20:12:24 -0000 Re: request for font utilities, Greg Haerr
Next in thread: 6 May 1999 20:12:24 -0000 Re: request for font utilities, Ben Pfaff


Powered by ezmlm-browse 0.20.