Flickering font from random generation of font types

Programming Questions

beth45

Flickering font from random generation of font types

in Programming Questions • 1 years ago

With the random function, I have created a simple algorithm to generate a different font type every time I run the program but the font flickers from one font type to the other when I run the program because draw () keeps calling back the random function.

class WordCollage extends InteractiveBoxes {

PFont font1, font2, font3, fontR;
String word1;

// constructor of the Picture Gallery class

WordCollage (int boxPosX, int boxPosY, int boxPosW, int boxPosH) {
    super (boxPosX, boxPosY, boxPosW, boxPosH);

    font1 = loadFont("VinerHandITC-48.vlw");
    font2 = loadFont("SegoeScript-Bold-48.vlw");
    font3 = loadFont("BradleyHandITC-48.vlw");

    word1=(textbox.getWord());

} // end of the constructor

void display () {
    float rF =random(1, 3);
    int randomFont=int(rF);
    switch(randomFont) {
    case 1:
      fontR=font1;
      break;
    case 2:
      fontR=font2;
      break;
    case 3:
      fontR=font3;
      break;
    }
    fill(0);
    textFont(fontR, 48);   // Set the font type and size at
    text (word1, 700, 200);
}
}

Replies(4)

jbum

Re: Flickering font from random generation of font types

1 years ago

I assume, since you didn't post this in Exhibitions, that you don't like this awesome feature.

Well then, let's take the random selection out of draw(). Remove these two lines from draw():

float rF =random(1, 3);
int randomFont=int(rF);

Make randomFont a global variable (put it at the very top of the program).

int randomFont; // at top of program.

Then add these two lines to the end of setup()

float rF =random(1, 3);
randomFont=int(rF);

Since randomFont is global, both setup and draw can see it. It gets setup by setup, and it gets used (without being randomized) by draw(). Make sense?

beth45

Re: Re: Flickering font from random generation of font types

1 years ago

Well it certainly works beautifully when the variables are global. Thank you.

From the perspective of good programming though, is it not seen as a heresy to declare and initialize global variables for that are used for very localized purposes?

jbum

Re: Flickering font from random generation of font types

1 years ago

Feel free to stick 'em in your class, and initialize them in your constructor.

A word about globals though: I've been programming for a very long time, and I happen to disagree with that particular point of dogma. The lengths that people go to avoid global variables (in the name of making programs less prone to error) adds a lot of extra code, which in fact leads to a greater likelihood of error. A few well chosen global variables can make for a significantly shorter program, which has less risk of introduced error. I suggest you treat minimizing globals as a suggestion, rather than a rule.

If eliminating the global makes the code the same length (as it does in your example), go for it. But if adding the global makes the code significantly shorter, as it sometimes does, then consider using a global. It's silly to add a whole new class for the sole purpose of eliminating globals, for example.

I am well aware I hold a minority opinion, however.

If it makes you feel better: Processing wraps everything in an applet class, so technically, your globals aren't really globals.

Of course, if you are doing this for a homework assignment, then you better get rid of the damn globals, 'cause your teacher is probably steeped in dogma.

beth45

Re: Re: Flickering font from random generation of font types

1 years ago

Point well taken, jbum. It's good to know how people think things through when the dogma can be put aside. Official sources of information for what good programming is are unfortunately not as varied as first-hand experience can be...

I appreciate the fresh perspective.

Top Reply