I was worried about that as well, so I tried it at the lower resolution first and then the higher one. It didn't really make any difference since it's a straight, not anti-aliased font. It is probably too small anyway though. I can read it fine but then I have fairly good eye sight.the text also looks like it'll be too small to read. On an iphone 4 it will be easy, not so convinced for the lesser versions
The joke was supposed to be that array indexes start at zero...the letters changing their boldness a lot would make it harder to read, at this zoom level it's readable but not fast. (at least that's what i think anyway)
it wouldn't make sense to start from level 0 and go straight to 2... if you went 0, 1, 2, 4, then it would make more sense... after all, 1 is also a power of 2...
I see what you mean, I've increased the size and have pretty much gotten rid of that problem now.yeah but thats a weird joke. it's proper to start at level 0 you see... so missing out 1 would just be totally weird
boldness, eg, the 'o' in other is different to the 'o' in or
Ah, thanks for pointing that out, it's if you collide with too much data you'll have to be resent from RAM.Just a logistical question, which might be worth waiting for actual gameplay to ask, but whatever...
You've got "collisions with other data" will cause you to be "resent from RAM" and... "collisions will also slow you down"
Which is it?
Nope; just translating UIimages.I assume you're doing that with CALayers and CAAnimations?
Good idea but it might be a bit tricky to tile without looking repetitive or being really big. Also, wouldn't make much sense having a PCB behind the full length of a memory bus.What about some circuitry? PCB?