Author Topic: Infrael - IWB for linux  (Read 9027 times)

Offline wizgrav

  • *
  • Posts: 15
  • Karma: +0/-0
    • View Profile
on: January 12, 2009, 04:27:29 AM
This is a python script for IWBs. It requires python(2.5+) and the pybluez, wxpython, xlib modules.
You can find it here. The wiki section has some documentation as well. Please post your feedback.



Offline wgrube

  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Reply #1 on: February 05, 2009, 08:51:51 PM
 :D
Hi! I'm new here and I've just installed infrael and it works fine! But I have some questions (sorry if they are stupid).
When I working with some graphical software (kpaint for example) the response is a little bit slow, so it takes about half a second to the cursor to get in place and start drawing (or mark a point), is this normal or can it be adjusted somehow? Also I've noticed that sometimes you click on a certain region of the screen and the cursor crawls slowly from the upper center to the point you clicked. Only after moving the pen a little with the button pressed it grabs the cursor and starts drawing. Do I have to do some adjustments? And, if so, how do I do it?
Sorry again if I'm bothering you with basic questions (or stupid ones)...



Offline wizgrav

  • *
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Reply #2 on: February 06, 2009, 02:20:55 AM
No you don't bother me at all, I'm glad you ask. The behavior is a bit different from the other apps. When you click somewhere, mouse events are recorded internally to the app but not generated. If you start a drag operation(no cursor visible yet) the app generates a mouse down on the original point you had clicked, replays the recorded movements and then it's dragging as usual. If you don't drag enough a mouse_down/mouse_up is generated when you release the pen, that's single clicking. If you hold the pen on and stationary for half a sec, the pointer warps close by to indicate that a right click was armed for next pen release. There's a small bug there and you should move the pen a bit when you see the pointer warping to force it to come to you faster. If you hold this triggered state for 3 secs a left mouse down will be generated at the point the cursor currently resides so you can do some precision clicking/dragging. It's a bit weird setup but I find it to be a functional compromise considering the nature of the wiimote's feedback. Nevermind the command and motion data, these will go and a gesture system that utilises a second pointer will come instead. Along with multiple screen support which are the features I'm currently working on