The app writes numbers to iPad screens, how can I prevent this?

Question

EDIT: my code for this is actually open source if anyone can watch and comment.

I might think that this could be a problem: with a special font, using a bright green color, refresh the shortcut too fast?

Repo: https://github.com/andrewljohnson/StopWatch-of-Gaia

Class for timestamp: https://github.com/andrewljohnson/StopWatch-of-Gaia/blob/master/src/SWPTimeLabel.m

The class that starts the timer to update the label: https://github.com/andrewljohnson/StopWatch-of-Gaia/blob/master/src/SWPViewController.m

==============

It is reported that the My StopWatch application is reported to be recording several iPads for time periods. Does anyone have a suggestion on how I can prevent this screen constancy? Some famous workaround for removing pixels sometimes?

I constantly get emails and you can see numerous reviews here: http://itunes.apple.com/us/app/stopwatch+-timer-for-gym-kitchen/id518178439?mt=8

Apple cannot advise me. I sent an email to appreview and I was told to submit a Technical Support Request (DTS). When I filled out the DTS, they told me that this was not a problem with the code, and when I asked for help from DTS, the "senior manager" told me that this was not a problem that Apple knew about. He also advised me to record an error with the Apple Radar tracker, if I think this is a real problem.

I filed a Radar error a few weeks ago, but it was not confirmed. Updated radar link for Apple employees, for notes for notes rdar: // 12173447

Answer 1

Actually, this does not “light up” on a display other than CRT, but some types of LCDs may have problems with saving / saving the image.

One way to avoid both is to move the image around very slowly, much more slowly than the screen saver. If you move the clock panel around a small amount and very slowly (say, a few minutes to make a complete outline of just a few tens of pixels), the user may not even notice it. But this movement erodes all thin lines and sharp edges over time, so even if there is resistance, the absence of sharp edges will make it difficult.

Added: There is also one (unconfirmed) report that blinking pixels at full frame rate may increase the likelihood of this problem. Thus, any textual / numerical updates in place should occur at a more humanly readable pace (say, from 5 to 10 frames per second instead of 30-60 frames per second) if they are repeated over very long periods of time. An application can always update the final number to a more accurate count, if necessary.

Answer 2

A “burn” is due to the emission of phosphorus in a CRT. LCDs cannot be lit because they do not use a phosphor.

Most likely it is image retention / Image persistence . The image may remain “stuck” on the screen for up to 48 hours. Usually it should not last so long, so this may be a lack of equipment. MacRumors has a topic about keeping the iPad , it discusses exactly this problem. As for the solution, you cannot do anything with the actual screen, because that is just how the LCD works. What I would like to try if you are still worried is using more subtle colors. If something does not actively change the pixels (I think the screen saver), you can not completely fix the problem.