Archives / Search ›

AntiRSI 1.4njr2

Onne Gorter’s AntiRSI is a Mac OS X application which reminds you to take periodic breaks from typing. Along with my beloved IBM model M15 keyboard, it’s essential to my getting any work done at all.

However, AntiRSI had some problems. The animated progress bar displayed during breaks sucked CPU like crazy, causing problems if I was watching a video at the time. Breaks kept getting prematurely reset because AntiRSI thought I was typing when it was a program like VLC calling UpdateSystemActivity, trying to avoid triggering the screensaver. Finally, the break window was just plain ugly—look at those poorly antialiased corners.

The last problem was more of a missing feature. While programming, I spend enough time thinking that I’m generally pain-free even if I work all day; unfortunately, debugging, writing and system administration can be much more typing-intensive, so I have to limit my daily typing time in aggregate, but AntiRSI didn’t keep track of it.

Over the past few years I’ve fixed these issues, and since my previous emails offering patches have gone unanswered, thought the result might be useful to others: download AntiRSI 1.4njr2 if you’re interested.

Some screenshots:

Session timer in AntiRSI 1.4njr2 AntiRSI 1.4njr2 Preferences

If you have a Mac and don’t like AntiRSI, try Time Out: it’s much more customizable, but takes over the entire screen, making it unusable for me. According to a VersionTracker review, it also hogs CPU during breaks.

For Windows and X11, check out Workrave; it’s great, includes a session timer and even comes with network support if you use multiple computers.

2 comments on “AntiRSI 1.4njr2”

  1. 14 October 2007 | 1:58 PM

    Hey Nick,

    Thanks for this – I have been using it on my iMac at home. I have observed one minor bug – when on work break, there is a timing issue with the counter. As it counts down, the minutes remaining is decremented one second too early. The sequence that I have observed is:

    3:02
    3:01
    2:00
    2:59
    2:58

    Nothing affecting the functionality – just a minor visual flaw.

    Anyways, thanks for putting this out there!

    -Andy.

  2. 5 November 2007 | 4:40 AM

    Thanks for pointing this out. I never noticed it during development. I was not rounding when I should—yay floating point. It only affects display, not operation. I just posted 1.4njr3 with a fix.

Leave a reply