Thank you for checking! Do the games react to absolutely no button presses? Then it's more likely they don't open the js-device (maybe not configured to use a standard joystick/gamepad?).
I don't know if a PS3 controller creates a special device or a standard js-device. I will try to find out.
It sounds right, what you are doing. Is the Bluetooth button in MC turning green?
You could run "hcidump" (attached to #1 post) to monitor the pairing process and post the result here. This will give information, if the connection is working properly.
I've added a download (hcidump) to the #1 post. The tool monitors Bluetooth events and may help us to find the problem. It will produce a lot of output, so please use spoiler tags when posting here :)
If you didn't use a pin, then there is (of course) no authentication. So, that's ok.
If you had used a pin, you should have seen something like
Connections:
> ACL XX:XX:XX:XX:XX:XX handle 1 state 1 lm MASTER AUTH ENCRYPT
So, that's also not the problem.
I must admit, I'm a bit clueless right...
Looks ok. Let's check the connection. While connected please open a terminal on the Pandora and enter "hcitool con"
Please try this: Open "/etc/bluetooth/main.conf" and change "Class = 0x000100" to "Class = 0x000540". This should make your Pandora to be discovered as a keyboard instead as a...
Hmm, when the button is green, Windows has successfully detected the HIDs and connected. So far so good. But it does not react on input? No keyboard, no mouse, no gamepad?
Maybe there is a problem with the input. Please post the first few lines from the logfile...
There is a bug in the config file parser, which merges the two config files and removes new line tags. I gonna fix that.
The problem with the Fn keys is, that they are language dependent. But I will try my best.
I also get occasional segfaults. The debugger points me to the QtGui lib, so I'm...
Well, it's not planned, since you can use every text editor. And the syntax shouldn't be too hard to understand ;)
But I could assemble a list of all valid keys if that helps.
A new version is available: v1.0.1.1
Change Log:
- Gui
Added a status bar at the bottom of the window. This will be used to display
some information (currently only used for a few bluetooth messages).
- Bluetooth
Initiating a connection to a host has been disabled for now because this
could...
The HID mouse does not have a scroll wheel implemented (yet). Anyway, it would be difficult to differentiate between a "double left click" (nub up) and a "left click" (nub left). This would require to measure the time between clicks somehow, which is not supported. At least not yet :)
Thanks for your report. I can reproduce this. It will be fixed as soon as possible.
Looks like there are still problems with the start script. Please unload all "g_" modules by hand. That should fix the problem
Thanks for your input, people. I'll keep investigating the problems.
The touchscreen is not implemented yet. The action buttons shouldn't be a problem. Could you please post the map you tried?
A new version is online.
Change Log:
- Gui
Device and connection buttons are now functional
Enabling/disabling an input device will stop processing input events from that device
Enabling/disabling an output device will stop forwarding input events to that device
USB/Bluetooth buttons allows to...
Thanks for that info. That would be quite handy. I will check it.
Not yet. But they certainly will be.
The pnd doesn't start or stop bluetooth. If bt is disabled, it simply won't be used :)
The buttons are currently without function. They will work in the next version.
In fact the the right nub's middle button (think it's down position) is mapped to the mouse middle button. Also shoulder buttons are mapped as right and left buttons. So that's intended behavior.
To check that...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.