Thanks for the quick reply!

Don't misunderstand me, I'm not suggesting it's a fault with RB as such. Rather a fault possibly in my understanding of how it works (which is still quite elementary). I've defined a behaviour in order to map the necessary keystrokes, thanks to help from the online video but am just wondering if there's anything I need to bear in mind or anything obvious that could be causing the problem. For example, it took me a while to work out NOT to send the keystroke for switching into Xhub directly to the app itself, for reasons which now seems obvious enough but didn't occur to me when first making the behaviour.

But thanks for the tip about the virtual remote! My case in point cos that's a subject I haven't explored yet and if it means a more realistic and accurate simulation of the Apple Remote, maybe that's exactly what I need. But can I somehow integrate that with the eyeTV remote? I'll RTFM for that ;-)

I'll definately write the author or post to a forum for Xhub too, but I could also imagine the reply is "not a bug with Xhub" because, as I wrote, both Remote Buddy and Xhub operate fine each in their own right. The problems only start when I start trying to glue them together with my own custom behaviour.

I'd love to get this all working though because since my HTPC is based around eyeTV and Remote Buddy is the only remote control software to support the eyeTV remote and Xhub the only mediacenter to integrate eyeTV it seems to be the perfect combination?!

Just as an aside; XHub comes with plugins for various remote software, but unfortunately not RB (hence me trying to roll my own). Ever thought about distributing an Xhub behaviour this way?

Cheers, 
Rich