Jump to content
Flirc Forums

GrumpyEngineer

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GrumpyEngineer

  • Rank
    Curious Flirc-er

Profile Information

  • Gender
    Not Telling
  • Location
    Southampton, England
  1. a number of remotes (including mine) behave this way. the reasons for this and the solution are in this thread... rich
  2. curently we can erase the IR codes one at a time, given that with certain remotes we have to program each button twice it'd be nice to click erase and then click a key on the virtual keyboad and have that erase all IR code associated with it. so if you had a problem with the behaviour with the up arrow, for example, you could click erase, then the up arrow on the virtual keyboard and every IR code associated with it would be deleted so you could just remap that key again without it undoing anything else. i guess its more of an issue for those with things like the xbox remote which need each button programming twice because you have to erase each button twice and things start to go horribly horribly wrong if you only erase one of the two IR codes. rich
  3. the 'parent dir' and 'back' buttons in the flirc xbmc giu window both get mapped to backspace key. internally to xbmc, backspace is the default key for 'back' and 'parentdir' is classified as an 'action' that can be called/mapped but doesn't have a default key assigned to it so it kinda doesn't make sense for it to have a button in the flirc gui, especially if it gets mapped to backspace which is already covered by 'back'. for consistancy the parentdir button in the gui should be removed. rich
  4. hmmm, looking at this a bit more closely, the 'parent dir' and 'back' buttons in the flirc xbmc giu window both get mapped to backspace key. internally to xbmc, backspace is the default key for 'back' and 'parentdir' is an action that can be called/mapped but doesn't have a default key assigned to it so it kinda doesn't make sense for it to have a button in the flirc gui, especially if it gets mapped to backspace which is already covered by 'back'..if that makes sense rich
  5. 2nd time lucky...firefox crashed and ate my last reply been doing some more experiments. i 'erased' back a few times, i'm pretty sure it let me erase more then the 2 times i thought it was programmed but cant guarantee it, the erase process is quite slow so i may be guilty of not letting it finish properly before i tried to erase again. anyway, after that i had to reprogram the 2nd press of the numeric and direction keys again. i did a 'clear config' and started again and now its behaving perfectly!!!! i'm not sure i understand the difference between 'back' and 'parentdir' in the firlc xbmc gui, they seem to be the same thing in the skin i'm using. to clear up another issue, i managed to program the remotes 'pause' key to show cpu information without any problems unlike the other caller pseudo7 mentioned. there are 2 xbox remotes, an older black coloured remote and a new white one called 'Xbox 360 Universal Media Remote' which i have. perhaps there is a difference between the two ? i've not gone through every button on the remote yet to see what works and what doesnt but all the standard xbmc buttons can be mapped along with the red/green/blue/yellow buttons which i use to cycle through audio tracks and subtitles and now i've jinxed it.... i realised i had programed 9 into 7 and 7 into 9 so hit erase, then 7 and it said key erased, so it did it again for the 2nd key press and then again and again and after about 8 times it finally said key already erased and then nothing worked. it says key programmed but nothing happens in notepad etc. had to restart windows and the problem has cleared its self...windows, dont you love it? anyway its all good now after the restart :)
  6. i've been trying to get the new xbox 360 (rc6) remote to work with filrc and xbmc on a windows7 pc. initially i had the 'double key press' problem which i managed to work out myself before finding it on the forums, i correctly guessed it was that the remote was giving out slightly different codes on each key press but to me it wasn't immediately obvious that you could program multiple remote buttons to a single keyboard key. the xbox remote can be programmed to control the tv too however the volume +/- keys seem to give the same code when the remote is in tv mode or xbox mode so when i hit volume up both xbmc and the tv responded to the key press and i ended up with no sound. solution to this is just unprogram the volume keys from flirc so that just the tv responds, i've never used the volume function in xbmc and really only programmed them into flirc in the first place because the option was there in the xbmc screen. when i erased the vol +/- buttons in flirc i had to do it multiple times because the double key press issue meant that i had programmed each one with all the different codes that the remote gives for the same button. however once done the four direction keys went back to needing a double press again and so needed reprogramming. obviously something like this would be hard to reproduce and i cant rule out user error. what would be useful is instead/as well as the current option to erase an individual key press on the remote is an option to erase all codes associated with keyboard function ie in the gui, click erase and then click vol+ and it'd erase all ir codes associated with vol+ rather than have to individually erase all ir codes via remote presses. operation is perfect in xbmc now except for one thing, if i'm in file mode and i hit 'back' which is supposed to jump up one directory 9 times out of 10 it will jump all the way back to the home screen. it feels like an over eager auto repeat on the key press but cant work out whether its a function of the remote, xbmc, windows or flirc. i don't want to suggest that filrc has the option of disabling auto repeat on individual keys when its nothing to do with it in the first place so if anyone has any suggestions as to what is going on there then i'd like to hear. having suffered the limited functionality of the xbmc android remote (it works perfectly but needs more keys) and having sent back 3 motorola nyxboards because of range and 'left click' issues my first couple of days of flirc ownership have been a pleasant change. rich
×
×
  • Create New...