centering custom font

BTW, one of the things I've done for the A and P, is figure out the width of the "hh:ss" and then use a different font for the a/p and position it based on the width of the time.

This is how I was doing it before, utilizing the XTINY and just showing "P". But there was some drawing issues with it, the P's position wasn't being updated when the time was updated, so when 9:59 turned to 10:00, the last 0 would draw on top of the P. Conversely, 12:59 to 1:00 let the dude straggling off by himself. :\
I really liked doing it this way, I felt the P was far less intrusive, but hated this loitering of the character. Additionally, on different watches, its alignment would be off. It really irked my OCD ;Þ

You should not have to change your code (other than to reference the new font) to get this to work correctly. Have you tried to go back and regenerate your font with different options selected? Did you try using the options shown in the Fonts section of the Programmer's Guide?

Went back and tried it again, I had one of the drop downs changed to something other than "glyph"
I'll give it another shot.

I see it as a bit of a style/readability thing.... Since they are bits, (0,1,2,4), using "+", to me it reads that I'm doing both of the justifications (horizontal plus vertical), while if I see "|" or "or", it could be one or both (& would result in 0, so that shouldn't be used though)

As I said, this isn't really a problem for the expression you're looking at. For you, an experienced programmer, this is not a problem. For a guy just getting started, it will end up being a problem after they copy your code and modify it later not realizing the consequences of using addition where a bitwise or was more appropriate. For most people, it is easier to learn rules if they are simple and there are few exceptions. For them it is typically much simpler to learn to use use bitwise operators when dealing with bit masks, and just leave it at that.

For those who are following this discussion, here is an example of why using addition to combine bitmask values can cause problems.

class Thing
{
enum {
REQUIREMENT_1_SATISFIED = 1,
REQUIREMENT_2_SATISFIED = 2
}

hidden var requirements = 0;

function satisfyRequirement1() {
requirements = requirements + REQUIREMENT_1_SATISFIED;
}

function satisfyRequirement2() {
requirements = requirements + REQUIREMENT_2_SATISFIED;
}
}


Now consider the following code...

var thing = new Thing();
thing.satisfyRequirement1();
thing.satisfyRequirement1();


The result would be that requirements indicate requirement 2 had been satisfied, even though it had never been. If the bitwise or operator was used, this would not be an issue.