This posting is older than 6 months and can contain outdated information.
Actually, the remote ID that Remote Buddy 1.11.4 and previous
versions
send is 168. It's a bug I didn't notice until now.
That's interesting - both Ryan and I saw PlexHelper reporting that
it had received button presses on 168 sometimes, and on 150 other
times. So it looks like the code sort-of-worked sometimes.
You really should only have seen 168 as the code was consistently
stored at a different location (*) than was being looked for, so that
RB used the default value of 168 instead. This of course only applies
when RB is actually running. If you find a way to get codes other than
168 while Remote Buddy is running, please let me know.
Those are the kinds of bugs I love trying to hunt down. ;) Thanks,
I'll be looking forward to the next release. Any chance it'll be out
within the next two weeks or so, before my trial period runs out?
It should be available before that.
Best regards,
Felix Schwarz
(*) essentially, I wrote [dict objectForKey:@"x"] instead of [[dict
objectForKey:@"y"] objectForKey:@"x"]