Click in the nick column to highlight everything a person has said.
The icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

indeed, it was hard to find a button for "resume" on the c200 and comes with the drawback that you can't force horizontal scrolling in the lists (to the right). It's probably on "Play" or something more suitable on the H100

The Nano1G didn;t seem to have much of a problem running it to begin with, and I don't recall what fps it ran at formerly...but it feels a lot smoother. I see the same changes in fps on the 2G that you do, however.

It would be great if somebody could test it on a player with <=64 vertical pixels, since Chopper uses a different speed for those. I tried to keep the speed the same, but the Nano2G is my only player so I couldn't test it.

yes but the apps code reading the buttons is often designed as a loop that asks for a button and then does some things, this has a timeout to avoid spinning like crazy, if that timeout is long, pressing a button will make things happen noticably quicker