Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

usb-driver.py either left mouse button down or up? #14

Open
o-jasper opened this issue Aug 14, 2018 · 3 comments
Open

usb-driver.py either left mouse button down or up? #14

o-jasper opened this issue Aug 14, 2018 · 3 comments

Comments

@o-jasper
Copy link

Presumably blue.py does the same, because this aspect of the code is the same.(but i haven't gotten bluetooth to pair)

When you start it the left mouse button is down, clicking it once with something else, the boogieboard does not affect the button down/up anymore.

Ideally you would be able to move the mouse by hovering and click pushing down. Perhaps with some config allowing a pressure threshhold. (Maybe stdout could be an option too)

So tried xev,(after trying gimp) it doesn't seem to produce any events, not even motionevents! But the mouse does move. (and generates events exitting/entering the window)

@jbedo
Copy link
Owner

jbedo commented Aug 14, 2018

Strange, you should be able to hover and "click" by touching the pen to the tablet. There should also be pressure sensitivity. What parts are working? You can move the cursor but touch/pressure doesn't register? What about the stylus button?

@o-jasper
Copy link
Author

Maybe it is my stupid setup... For some reason i can't make a Xorg.conf or make X detect it(or leave it absent and have X detect)

Also i was running usb-driver.py from TTY, but tried it on the same TTY and it does not seem to matter. I had to run it as root to have sufficient permissions.

Bit worried i am wasting your time.. Still, strange that moving works but it doesn't register movement events.. So basically, no events at all.(not stylus either)

@jbedo
Copy link
Owner

jbedo commented Aug 20, 2018

You could add some print statements to inspect "touch" and "pressure", then you'd know if it was an issue getting the events from your boogie board or if it's the uinput configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants