JadeMonkee wrote: > Ok I thought I'd have a go at it, but I haven't had much luck. > I started by doing the following (as per this post > https://forums.slimdevices.com/showthread.php?105117-lirc-rpi-gpio-IR-support-for-picoreplayer&p=883651&viewfull=1#post883651): > > Code: -------------------- > > sudo mkdir /home/tc/.jivelite/userpath/jive/ > sudo cp -L /opt/jivelite/share/jive/jive/InputToActionMap.lua /home/tc/.jivelite/userpath/jive/InputToActionMap.lua > cd /home/tc/.jivelite/userpath/jive/ > sudo vi InputToActionMap.lua -------------------- > > > > Then added below the existing entries in: > keyActionMappings = {} > keyActionMappings.press = { > (but before the final closing bracket) > > Code: -------------------- > > --BEGIN my OSMC Remote mappings. I've commented out existing maps > --event1 keys > --[KEY_HOME] = > --[KEY_UP] = > --[KEY_DOWN] = > --[KEY_LEFT] = > --[KEY_RIGHT] = > --[KEY_ENTER] = > --event2 keys > [KEY_INFO] = "go_current_track_info", > --[KEY_BACK] = > [KEY_CONTEXT_MENU] = "volume_up", > [KEY_PLAYPAUSE] = "pause", > [KEY_STOP] = "volume_down", > [KEY_REWIND] = "jump_rew", > [KEY_FASTFORWARD] = "jump_fwd", > --END my OSMC Remote mappings -------------------- > > > > Backed up my changes via the web menu and rebooted. > But Jivelite doesn't even start. > As soon as I RE-copy a fresh version of > /opt/jivelite/share/jive/jive/InputToActionMap.lua into > /home/tc/.jivelite/userpath/jive/InputToActionMap.lua Jivelite > immediately starts. > > What have I done wrong? > > Thanks for your help - and sorry for taking up so much of your time! Jivelite will fail to start if you use KEY_ names that are not defined. Unfortunately, the list is created an compile time and can't be extended without rebuilding jivelite.
The mappings and action keys are defined in these jivelite files. https://github.com/ralph-irving/jivelite/blob/master/src/jive.h https://github.com/ralph-irving/jivelite/blob/master/src/jive_framework.c https://github.com/ralph-irving/jivelite/blob/master/share/jive/jive/ui/Framework.lua The scancodes reported by evtest are from the kernel and the mapping to the SDLK_ names happens in https://github.com/ralph-irving/squeezeplay/blob/master/src/SDL-1.2.15/src/events/SDL_keyboard.c https://github.com/ralph-irving/squeezeplay/blob/master/src/SDL-1.2.15/src/video/fbcon/SDL_fbevents.c It's very convoluted. You need to find the keycode for the media keys and try to find it in the SDL files and then use the KEY_name in InputToActionMap.lua mapped from the SDLK_ symbol. In my experience a lot of the low cost wireless keyboard/remotes use non standard keycodes that require changes to both the SDL library and jivelite to work. Ralphy *1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio 'Squeezebox client builds' (https://sourceforge.net/projects/lmsclients/files/) 'donations' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted) always appreciated. ------------------------------------------------------------------------ ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484 View this thread: http://forums.slimdevices.com/showthread.php?t=103330 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
