I say avoid analogue clocks. People younger than I am are less and less likely to be able to read an analogue clock. In point of fact. I have to decipher them.
This means I can't 'read' them. I can figure them out, the same way I can figure out a word I've never read before. But it takes a lot more time. If you simply must have a clock, and it can't move. I'd do any or all of these things: (some people have already said) -Alter the color over time. -Use a font or fonts that activate the widest set of pixels. -Swap the font around over time. -Slowly move the clock. But really... if you want to eliminate burn in entirely. Just revert the display once a minute. Make the off pixels on, and the on pixels off. This will prevent burn in, as all the pixels will get exactly the same amount of wear, and it will also alert the user that the minute flopped, which is pretty handy if you are timing something by hand. This also works with very small displays. If the display is dot-matrix, this works. Just be careful about the font, text needs to be thicker to be easily read in revert. Anyway. That's my 2 cents. Will . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=35445 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
