Bug 475 : textAlign(CENTER) with P3D and OPENGL produces messy result
Last modified: 2009-09-05 20:12




Status:
ASSIGNED
Resolution:
-
Priority:
P2
Severity:
normal

 

Reporter:
crispin
Assigned To:
fry

Attachment Type Created Size Actions
attempt to reproduce the problem application/zip 2007-01-03 12:01 37.21 KB
This should reproduce the problem application/x-zip-compressed 2007-01-03 12:42 7.78 KB
Fix for bug 475 patch 2009-09-05 20:12 693 bytes

Description:   Opened: 2006-12-30 11:22
Using WinXP and the processing 021 -

--
textAlign(CENTER);
text("4",width/2,height/2);
--

This may or may not produce a noticeable 'fuzzy' effect on the text
depending on the length. Does not occur with textAlign(CORNER), and occurs
with any font.
Additional Comment #1 From fry 2007-01-03 12:00
hm, i can't seem to reproduce this with the attached sketch. can you verify
that this remains a problem with processing 0123?

there's no such thing as textAlign(CORNER), for what it's worth.
Additional Comment #2 From fry 2007-01-03 12:01
edit]
attempt to reproduce the problem

this doesn't seem to show the problem (at least on rev 123 on macosx)
Additional Comment #3 From crispin 2007-01-03 12:42
edit]
This should reproduce the problem

Thanks for your help, this should (hopefully) demonstrate the problem... Again,
I am using WINXP.
Additional Comment #4 From fry 2007-01-03 12:51
k, confirmed and updating the bug title to cover the actual issue.

the issue is probably something to do with character placement when
fractional values are used for the position, and will affect any images
drawn with P3D or OPENGL as well.
Additional Comment #5 From crispin 2007-03-06 23:19
Hi,

If by fractional values you mean float values, then I don't know, I never
set my text positions that way. I haven't noticed this effect with images
as you suggested. If I use P3D instead of OPENGL the effect is that
instead of blurring, pixels are missing from places in the text so it is
unreadable. If I don't use P3D or OPENGL, then the text comes out
perfectly. Unfortunately, this isn't a viable option.

Cheers,
C
Additional Comment #6 From MrFeinberg 2009-09-05 20:12
edit]
Fix for bug 475

Well, this fixes the problem, but at the cost of accuracy.