BitBlt>>primDisplayString no longer updates destX?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

BitBlt>>primDisplayString no longer updates destX?

Andreas.Raab
 
Folks -

I just realized that BitBlt>>primDisplayString no longer updates
BitBlt's destX var. I'm not sure when or why this was changed but it
explains some of the strangeness that has been noticed with m17n font
display recently (some glyphs are just printed on top of each other).

I would like to fix this ASAP since to me that's a critical piece of
code and uncommenting the primitive is painfully slow.

Any ideas what was changed and why?

Cheers,
   - Andreas
Reply | Threaded
Open this post in threaded view
|

Re: BitBlt>>primDisplayString no longer updates destX?

David T. Lewis
 
On Sat, Aug 15, 2009 at 11:05:09AM -0700, Andreas Raab wrote:

>
> Folks -
>
> I just realized that BitBlt>>primDisplayString no longer updates
> BitBlt's destX var. I'm not sure when or why this was changed but it
> explains some of the strangeness that has been noticed with m17n font
> display recently (some glyphs are just printed on top of each other).
>
> I would like to fix this ASAP since to me that's a critical piece of
> code and uncommenting the primitive is painfully slow.
>
> Any ideas what was changed and why?

The most recent change to #primitiveDisplayString is stamped 5/31/2008
by 'dtl', which certainly looks suspicious on the face of it, but the
change is minor and unrelated to destX. The prior version is from
4/3/2005, so any functional change has probably been in the primitive
for a number of years.

Dave