Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by yawor

  1. @teedoe sorry, as I've mentioned before I'm not using SMS-style input at all. When I really need to write something outside of XBMC then I just use a wireless keyboard. I just pointed it out that there is such functionality in EG as I've stumbled upon it checking what plugins are available.

  2. @teedoe this has nothing to do with the Flirc itself. The software presented in the thread you've linked in the fist post is a 3rd party one, written by the NJKA (the author of the thread you've linked to). If you need such functionality you need to contact with the software author himself or find another solution. You probably could use EventGhost software as it has a plugin to do SMS-style text input but you need to do some work configuring it. I'm not using this plugin so I can't tell you much about it.

  3. Ich habe Windows 7 32 bit

    in der Flircsoftware erscheint keine Firmwareversion und die Meldung pleas connect flirc

    von Windows wird der Stick erkannt und die Treiber Installiert. Dieser wird dann im Gerätemanager aufgeführt.


    Could you use English? I don't think that there are many people here speaking German who can help you.

  4. Have you tried other USB devices on this new computer under Linux? Maybe the problem is with the motherboard hardware and not with the receiver itself.


    Flirc works by emulating USB HID keyboard so it SHOULD work as long as a normal USB keyboard also works.

  5. Actually you don't need to learn from MCE remote. You can set up Simple 4 remote with MCE setup code using simpleset.com website :) (at least european URC-6440 can be set up this way, I think there was some strange problem with OARUSB04G). I'm also actively working with experts from http://www.hifi-remote.com/forums/ which is a community of EUI/OFA remotes modders (these remotes can have very advanced features) on supporting these new "SimpleSet" (like Simple 4) remotes and I think that we will release something really soon. The software we are working on allows to edit remote's configuration in much greater details.


    As for 3 you can always use some kind of script or software to map mouse movements to specific keyboard shortcuts and map those shortcuts to remote buttons.

  6. You are running old firmware and gui. You can upgrade firmware from new version of the gui (menu File -> Advanced -> Force FW upgrade). There is always a question that if everything works OK for you then is there a reason to do upgrade. If it works for you don't break it :).

  7. 1. As long as you can associate script with a keystroke it will work. But remember that you can't associate the script with keystrokes from the Flirc only so pressing the same key combo on a normal keyboard with also run the script.

    2. You can't disable Flirc, but you can always make a script that will capture all mapped keystrokes and block them. This will of course also disable the same keystrokes on a normal keyboard.


    If you want the more advanced solution which I'm using I can help you with the setup, but it's on your own risk. Also this method requires that the GhostEvent is always running in the background as in my solution Flirc no longer acts as a keyboard. If you are interested please contact me using private message when you decide to buy Flirc because I would like to keep it not public for now (I need to test it more and wait for Jason's firmware changes to see if it breaks it or not).

  8. How does this behave when you connect a normal keyboard to the Ouya? Are you able to move around with cursor keys? Please remember that Flirc acts as a keyboard so Ouya probably is expecting text input from the keyboard as opposed to the method used when text is entered using gamepad.

  9. Hi,


    1. Short answer: with just Flirc, no.

    Long answer: Windows doesn't have ability to easily recognize on which keyboard a key was pressed. This means that Flirc, which works like a keyboard, can only send key presses to currently focused application. There are some work-arounds but they are not reliable. There are 2 APIs in Windows for key presses. First API allows to capture key press so it's not visible by other apps in the system. Second one allows detecting key press source (so app can recognize that it came from Flirc) but it cannot capture the key so it is still sent to the focused app. There where some projects that tried to connect both APIs but it is VERY unreliable.


    There is another way but it's not easy and not officially supported. There is a way to set up the Flirc not to use normal keyboard codes but a more generic HID codes from a different HID table. This allows to go around default keyboard filter in Windows allowing some more advances usages. I'm using Flirc that way but you need some software to catch HID codes from Flirc and do something based on them. For that I'm using GhostEvent with a little modified HID plugin (I've modified it myself as there was some problem with default plugin). This method is hard to set up because it involves editing config file saved from Flirc. I would probably not recommend this method because it is possible it can be broken by some future Flirc firmware upgrade.


    2. Flirc wouldn't know when you are using Netflix on your TV. Actually nothing on your PC would know that unless your TV can somehow provide it with such info. You would still need some way to decide if you want to accept Flirc input or not.


    3. It can learn up to about 169 remote buttons and assign them to key combinations (a key combo is a zero or more key modifiers - like shift, ctrl - and exactly one normal key). But it also depends on things like protocol used by the remote/keyboard as not all protocols work good with Flirc.

  • Create New...