Hallo,

I tried to hack a little script to access dcop or dbus applications via the remote, and noticed that I dont know what the events of the remote keys are called. So I searched on the net, but could not find anything.

for i in range (0, 64):
    print tux.event.remote_key_to_string(i)

gave me the following information:

K_0
K_1
K_2
K_3
K_4
K_5
K_6
K_7
K_8
K_9
None
None
K_STANDBY
K_MUTE
None
None
K_VOLUMEPLUS
K_VOLUMEMINUS
K_ESCAPE
K_YES
K_NO
K_BACKSPACE
K_STARTVOIP
K_RECEIVECALL
K_HANGUP
K_STAR
K_SHARP
K_RED
K_GREEN
K_BLUE
K_YELLOW
None
K_CHANNELPLUS
K_CHANNELMINUS
K_UP
K_DOWN
K_LEFT
K_RIGHT
K_OK
None
None
None
None
None
None
None
None
None
None
None
K_FASTREWIND
None
K_FASTFORWARD
K_PLAYPAUSE
K_STOP
K_RECORDING
K_PREVIOUS
K_NEXT
K_MENU
K_MOUSE
K_ALT
None
None
None

So, these seem to be the key_events which do not throw an error when you enter them into the key_to_string function.

substracting the "None"s from the total of 65 leads to 45 valid keys. when I count the keys on my remote I get to 44.

This somehow matches. Maybe this is of help for someone.

I think this could have been published somewhere.. wiki, forum, faq or docu...

greets

Bastian

Hi,

I've found the list of remote control keys in the documentation, but i guess it's somewhat hidden in it :p

http://www.tuxisalive.com/documentation/tutorial/tux-api-documentation/event-class