Jump to content
Flirc Forums

Tobbe

Members
  • Posts

    1
  • Joined

  • Last visited

Posts posted by Tobbe

  1. On 10/2/2015 at 3:40 PM, yawor said:

    Even though the Flirc itself can work with any system keyboard layout, the GUI is designed to support only US QWERTY compatible ones. The specific devices controllers (like Kodi) and built-in profiles are also not compatible with non-QWERTY layouts so it's best to not use/disable them in such situation.

    I see that you use non-QWERTY keyboard on the PC (probably german QWERTZ layout). Do you also use non-QWERTY layout on OSMC? I also use OSMC but I don't remember if there's an option to change keyboard layout anywhere (because polish keyboard layout is US QWERTY compatible).

    You can still use the GUI to program Flirc but it requires some extra work. You need to use the full keyboard controller in the app but don't look at the labels of the keys. Just ignore them. Look at your PC keyboard where exactly is the symbol (like +, -, or some letter or number) you want to record in Flirc (the row and how many keys from either side) and if it requires some modifiers like Alt, Ctrl etc. Then use the same modifiers and the key at the same position in the GUI (the same row etc).

    For example you have - (minus) sign next to right shift button (/ and ? on QWERTY). If you want to use minus with Flirc on QWERTZ you need to record a remote button for "/" key in the GUI because it is physically on the same spot on the keyboard.

    I hope I've described this enough. You can also look for my post about French AZERTY layout setup where I've also described this.

    Sorry for reviving this old thread but this bug is not very fun.
    Also problem is not a QWERTY vs others it is about the keyboard layout and ui userfriendliness.

    I got a swedish QWERTY layout and mapping volume down in "Kodi" section works but when i press volume down on the remote the volume up key in the gui lights up.
    So there is no consistency between what remote button you just mapped with what actually lights up after the mapping is done.

    This plus the additional guessing on the "full keyboards" screen with what key actually will generate the "-" sign to map it right.
    Surely the GUI must be able to figure out the current keyboardlayout or allow user to pick from afew options or include the numpad section (full keyboard includes numpad...)

×
×
  • Create New...