According to Line 10 of '/etc/default/bluez-utils' you can enable BT mice and KB's.

And everyone was wondering why I wanted to see hidden files...it's cause I'm bored at work!

I don't know if this is a great find, but a simple search led me to believe that nothing has been found on mice...so here you guys go. Mods feel free to delete this thread if it's useless...

Surely the showstopper with mice is that there is no cursor on screen? How would you know where you were clicking? Unless there is UI hack to show the pointer somehow?

Sure there is...Opera has a little clock that it shows...(Pointer?), I know I've seen it a few other times. There could be something that tells the cursor to hide when not active...couldn't there?

Well ... we can always try plugging a mouse in.

Yeah, perhaps, however the file I'm talking about refers to a Bluetooth mouse.

:::Anyone know if the method they say is the same as enabling BT keyboard?

Could this be another way maybe?

I got a powered USB hub working last night with my 770 in host mode (see my post in the accessories section for details).

I plugged in a keyboard and it just worked (no drivers). I plugged in a USB mouse and nothing. No cursor, tried clicking and dragging and got nothing.

David

Hmm, I just read that BlueZ is implemented in other distros as well, I'm guessing that there might be some sort of driver or something that is needed for it along with enabling it. Aside from that, it might also be different between USB and BT...no?

Just another data point:

If you open TuxPaint, there is sort of a mouse that works with the stylus.

I don't know what that implications for this might be, but for the person that plugged in the mouse, could they should try it with TuxPaint?

This was discussed in another thread, but I'm too lazy to find the reference. The conclusion was that the kernel does support mice (at least bluetooth mice, if hidd is running), but the X server (i.e. X windows) does not. The server does have a tantalizing "-mouse" option, but it doesn't work. So while a program can theoretically read mouse events itself, mice just aren't useful, at least not until someone builds a new X server that supports them.

Cheers, Lon

P.S. If there is some magic that enables mouse support in the server (i.e. if the above is wrong), then I would very much like to know what it is.

I actually investigated this very thoroughly, and as Lon has mentioned it doesn't work at the X server level. Getting a cursor to appear is relatively trivial, but doesn't buy you anything. Plugging in a USB mouse works perfectly in that all support is present to detect the mouse and automatically add this device as a command line argument to the X server . The only problem is that the X server has no support for more than one mouse. Trying to use a USB mouse as the primary mouse device causes the X server to crash, resulting in an automatic reboot. I suppose the digitizer protocol is different from the average mouse. I posted a question about this to the developer list but the silence was deafening.

Larry