the object 'g' is the PGraphics object of the sketch.

PhiLho  wrote on May 20^th, 2010, 1:05am:


That's not what I'm finding - and it's in line with the Help, which says 'Note that transparency levels are binary: pixels are either complete opaque or transparent. For the time being (as of release 0127), this means that text characters will be opaque blocks. This will be fixed in a future release (Bug 641).' I've found that alpha channels aren't being obeyed at all.

Thanks for the g suggestion, JohnG, I'll try that.

No, that's not my issue. Here's the code I was using (this is a method of a TextFormat class I've created):

void hDrawText(PGraphics tScope, String tString, int tX, int tY) {
   tScope.pushStyle();
   tScope.textFont(pFont, pSize);
     tScope.textAlign(LEFT,CENTER);
   tScope.fill(pCol);
   tScope.text(tString, tX, tY);
   tScope.popStyle();
 }

This was part of a general draw loop, which went something like this:
void draw()  {
 if (prog.hUpdate()) {
 pMain.beginDraw();
 prog.hDraw(pMain);
 pMain.endDraw();
 image(pMain,0,0);
 }
}
where pMain was an instance of PGraphics. Now I've replaced pMain with g and removed the beginDraw, endDraw and image lines.
When I used a buffer, the text looked horrible, with bits of antialiasing missing. As soon as I replaced it, it looked great. So there's definitely as issue there.

Completely off the point, holy crapola, Java's a horrible language when you're used to something as flexible as Lingo. Arrays in particular are just unpleasant. Irrelevant, I know, but I had to get it off my chest - I've been struggling with getting a HashMap from Strings to floats for the last hour.

I was just simplifying. There's an object heirarchy that leads to the drawText function. But yes, I do draw the background. And besides anything else, as I say, the real proof is that when I switched to using g instead of my own PGraphics object, with no other changes, the problem went away.

Get it?  Clarification?  OK, that was a bad pun.  

I wanted to jump in on this thread because I feel like using an offscreen buffer does have aliasing issues, and not just with text.  However, text provides a convenient testbed.  Here is a test I wrote, and the result.

Code:

// Test to compare:
// * Rendering text directly to screen
// * Rendering text to an offscreen buffer and placing on screen

PGraphics buffer;
PFont myFont;

void setup() {
  size(150, 100);
  buffer = createGraphics(150, 50, P2D);
  myFont = createFont("Verdana", 14);
}

void draw() {
  renderText(g, "Direct to Screen");
  renderText(buffer, "First to Buffer");
  image(buffer, 0, 50);
}

void renderText(PGraphics target, String string) {
  target.beginDraw();
  target.fill(0);
  target.rect(0, 0, width, 50);
  target.fill(255);
  target.textAlign(CENTER);
  target.textFont(myFont);
  target.text(string, width/2, 25);
  target.endDraw();
}

 

It's pretty obvious to me that one thing is not like the other.  But it's not clear why!

If I understand what's being said (and trust me, it's a good chance I don't!  ), then I think I'm doing it right by drawing a "background" of black behind the text.  If it's not a bug, then could you help me/us by fixing the code above?

Thank you!

I verified that using JAVA2D fixed the issue I was seeing.  Thank you!