 |
Author |
Topic: 2d text on a 'top transparent layer'... (Read 434 times) |
|
arielm
|
2d text on a 'top transparent layer'...
« on: May 1st, 2003, 6:24pm » |
|
don't get me wrong, i think that the 3d text in p5 is a WONDERFUL feature, but sometimes we need text that:
1- is simply 2d
2- is readable at small sizes
3- uses some custom font (okay, we can live without this one...)
4- doesn't require a lot of processing power to render
5- is always on top of the viewport and doesn't interfere with z-buffering...
6- is positionable using simple x and y coordinates, that are not affected by the transform matrix...
please take a look at:
http://proce55ing.net/discourse/yabb/board_Tools_action_display__num_1051796582.html
it's a good example to illustrate this need: a 3d view modifiable with sliders, with some (textual) parameters displayed on top of all...
the main problem is that with certain FOV or EYE-DISTANCE values, the text is "eaten" by the 3d model!..
|
Ariel Malka | www.chronotext.org
|
|
|
arielm
|
Re: 2d text on a 'top transparent layer'...
« Reply #1 on: May 4th, 2003, 12:05pm » |
|
well, maybe it is already possible to achieve...
playing with g.dimensions?
or maybe the mysterious FBF fonts could help?
|
Ariel Malka | www.chronotext.org
|
|
|
fry
|
Re: 2d text on a 'top transparent layer'...
« Reply #2 on: May 4th, 2003, 5:27pm » |
|
yeah, text support is really sucking overall right now. these are all points that we're aware of and hope to have at least some of them fixed for 1.0.
we have someone who's starting to work on at least part of it, so hopefully things will start improving.
|
|
|
|
|
fry
|
Re: 2d text on a 'top transparent layer'...
« Reply #3 on: Sep 24th, 2003, 3:59pm » |
|
this is implemented in rev 60. if you use:
BFont font = loadFont("somefont.vlw.gz");
textSpace(SCREEN_SPACE);
text(mouseX, mouseY, "drawn at screen resolution");
the font will show up in its natural bitmap sizes. and in rev 62, a font builder has been included, so that you can actually control the natural sizes of these fonts, which are currently all 48 point.
we're still trying to think of better solutions for the font issue, but it's a very difficult problem.
|
|
|
|
|
|
