FAQ
Cover
This is the archive Discourse for the Processing (ALPHA) software.
Please visit the new Processing forum for current information.

   Processing 1.0 _ALPHA_
   Programming Questions & Help
   Syntax
(Moderators: fry, REAS)
   text antiliasing problem
« Previous topic | Next topic »

Pages: 1 
   Author  Topic: text antiliasing problem  (Read 482 times)
bsr

WWW Email
text antiliasing problem
« on: Mar 26th, 2004, 4:44pm »

i'm having trouble with making small text appear clear.
 
i am using smooth() in the applet but am careful to switch it off before writing text to screen.
 
a rough test applet is here: http://hippocamp.net/misc/jmenu/test.html
 
is there a way round this? it makes the text look a little messy. is it the type of font being used? anyone else had this problem?
 
cheers,
jon
 

http://hippocamp.net
fry


WWW
Re: text antiliasing problem
« Reply #1 on: Mar 26th, 2004, 9:25pm »

text smoothing is in a bad spot right now, unfortunately.. i can't get to your applet, but if it's not 3D text, then i recommend using  
textSpace(SCREEN_SPACE);
which will let you draw text at its original size, directly to the screen. then you just generate fonts (sketch -> create font) for the sizes you need. it's not a great solution but works if you're doing 2D stuff and using just a small handful of sizes.
 
bsr

WWW Email
Re: text antiliasing problem
« Reply #2 on: Mar 26th, 2004, 10:01pm »

cheers fry, i'll give it a crack and once the codes progressed a little if i'm still having trouble i'll post it here (it's in a complete mess at the moment!)
 

http://hippocamp.net
gll

WWW Email
Re: text antiliasing problem
« Reply #3 on: Jul 2nd, 2004, 5:17am »

I was looking at this tread about the Function textSpace(SCREEN_SPACE) (Is there any Complete list of all "hidden" functions? - I've never saw that function before ) textSpace would be usefull, thx.
 
Please, have a look at :
http://www.vif.com/users/goo/P55/text/index.html
 
In this example I use two different Fonts (supertext10 and supertext20) to have two different sizes. Could we use textSpace(SCREEN_SPACE) and double the size, the pixel would be twice bigger?
« Last Edit: Jul 2nd, 2004, 5:18am by gll »  

guillaume LaBelle
arielm

WWW
Re: text antiliasing problem
« Reply #4 on: Jul 2nd, 2004, 3:04pm »

on Jul 2nd, 2004, 5:17am, goo wrote:
In this example I use two different Fonts (supertext10 and supertext20) to have two different sizes. Could we use textSpace(SCREEN_SPACE) and double the size, the pixel would be twice bigger

doesn't make much sense except for pixelized-like fonts (if your font were, say, Tahoma, it would be pretty useless to pixel-resize it twice...)
 
afterall, if you already manually crafted fonts at sizes 10 & 20, why not going on with higher numbers
 
another possibility: drawing your text on a BGraphics instance, which can be later on copied to screen with scaling (not sure about that, but there's maybe a parameter to affect the quality of scaling, i.e. smooth vs "raw")
 
hth
« Last Edit: Jul 2nd, 2004, 3:07pm by arielm »  

Ariel Malka | www.chronotext.org
gll

WWW Email
Re: text antiliasing problem
« Reply #5 on: Jul 2nd, 2004, 6:10pm »

Thx Arielm.
 
It was exactly for BitMap fonts. I like the aspect of the small fonts (superText in 10pt ) and keep it homogenous for all sizes. Kind of Harmonic pixel.
http://www.vif.com/users/goo/P55/TakyScreen/v06.html
 
When I create my font for 10 - 20 - 30... The size of the font increase which is redundant information. It's still a detail, GZed it give 3kB. I thought it was more.  
 
In http://bodytag.org/fasttext/ glen use bitmap. It would be easier to work in 3D (with voxels).
« Last Edit: Jul 2nd, 2004, 11:28pm by gll »  

guillaume LaBelle
Pages: 1 

« Previous topic | Next topic »