Not exactly; this is why we have two separate indicators in the TAP database here.

One lets you know if the TAP works with the original UK firmware, which has some very specific issues to do with the remote control keys.

And the other applies to TF5800s with firmware from May onwards. This has fewer issues, but it's still worth noting, since we don't have the same keys on our remotes, and some of the ones we do have are in different places. If a TAP relies on a key that's not available on the UK remote, then you'll have problems with it.

Keeping on top of all the updates is a nightmare too - our database needs a good tidying up at the moment.

The key codes themselves are mostly the same now. We don't have any keys that generate a different code when pressed, (unlike the original UK firmware).

The issue is more that a) we don't have all the keys - there's no UHF, for example - and b) our arrow keys and don't have dual functions. We have separate buttons for v+/v- and p+/p-, but as far as a TAP is concerned you can't distinguish between a left arrow and v-. So from a TAP point of view, we end up with two keys that do the same thing, and other keys missing.

And, then our coloured keys behave slightly differently, since they need to be available for MHEG applications. As a result of that, bookmark functions can only be accessed when the progress bar is on screen, which means some TAPs don't work properly.

So, a different keys.h won't help here. It's the same one.

If you want to allow for the original 5.11.52 firmware, then you need to look at the tf58keys.c code that we cobbled together. Even then, it's not a case that there are different codes per se. There are merely some strange mappings. Without doing some mapping back, you end up with really weird things like the Exit button decreasing volume each time it's pressed, and no way to turn it back up.

(Later...) Perhaps I'm remembering it wrong; I think it may be the case that the TAP sees the code for the key that you pressed, but to actually get that effect, you then have to pass on to the firmware the code for the key that's in that position on the TF5000. Which makes it really hard to have several TAPs running, too. Take a look at the mapping code, and you'll realise the grisly horror of the thing.