2013-01-02, 16:41
First thank you to the dev(s) for developping this excellent remote.
I'd like to ask the community whether some of you are successfully managing their XBMC without ever using (outside of configuration steps) keyboard/mouse, and without using a screen if playing back music, but using only the remote.
Basically I use XBMC quite often for music-only playback, and since I don't have a TV but a projector it is really unpractical to start it if I only want to play music.
This remote comes in very handy to get close to the mentionned goal, however there are some problems : quite often XBMC will pop "menus" or popup windows, that if you don't have a screen to view them are quite difficult to navigate out of. Basically any kind of error message that pops a dialog means trouble, as well as any input-based interaction.
Is anyone else using this remote as the main XBMC interface, and if you do what are your tips to minimize these types of "lock-ins" which require to actually start the screen ? I'm using XBMCLauncher which is quite nice to make sure XBMC is always on top of trouble that would come from windows, but that doesn't help with internal XMBC "focus-holders".
Cheers !
I'd like to ask the community whether some of you are successfully managing their XBMC without ever using (outside of configuration steps) keyboard/mouse, and without using a screen if playing back music, but using only the remote.
Basically I use XBMC quite often for music-only playback, and since I don't have a TV but a projector it is really unpractical to start it if I only want to play music.
This remote comes in very handy to get close to the mentionned goal, however there are some problems : quite often XBMC will pop "menus" or popup windows, that if you don't have a screen to view them are quite difficult to navigate out of. Basically any kind of error message that pops a dialog means trouble, as well as any input-based interaction.
Is anyone else using this remote as the main XBMC interface, and if you do what are your tips to minimize these types of "lock-ins" which require to actually start the screen ? I'm using XBMCLauncher which is quite nice to make sure XBMC is always on top of trouble that would come from windows, but that doesn't help with internal XMBC "focus-holders".
Cheers !