Page 1 of 2
Configurable Joystick - X,Y Pad
Posted: Fri Dec 09, 2016 10:09 am
by DaveyBoy
Hi all
Thought I'd share my latest creation with you guys, a configurable joystick - X,Y Pad:

Seems to work ok. Any hints or suggestions/advice appreciated

Re: Configurable Joystick - X,Y Pad
Posted: Fri Dec 09, 2016 10:57 am
by Spogg
I love it!
Really nice work and directly into my toolbox. Thanks for sharing.
Cheers
Spogg
Re: Configurable Joystick - X,Y Pad
Posted: Fri Dec 09, 2016 10:55 pm
by BobF
Hi DaveyBoy,
This works great, a really good job. Hope to see more from you in the new year.
Cheers, BobF.....
Re: Configurable Joystick - X,Y Pad
Posted: Mon Dec 12, 2016 1:56 pm
by DaveyBoy
Thanks for the positive replies guys.
I have a couple more little gizmos that I'll post soon

Re: Configurable Joystick - X,Y Pad
Posted: Mon Dec 19, 2016 11:56 pm
by brownts
Very cool!
Ok- so how do you go about using it as an input device?
Re: Configurable Joystick - X,Y Pad
Posted: Mon Dec 26, 2016 8:48 pm
by DaveyBoy
Oops.... I should have made it into a module
First post has been updated

Re: Configurable Joystick - X,Y Pad
Posted: Tue Dec 27, 2016 12:08 am
by RJHollins
Although I did get a RUBY error on 1st load, I reset the module, and now working.
This is really nice ... and stretchable with configurations.
Thanks !

mmm 1st request
Could you add a [CNTRL-MouseCLK] to reset to a default position ?

Re: Configurable Joystick - X,Y Pad
Posted: Wed Dec 28, 2016 12:25 am
by DaveyBoy
Hmmm, I don't get ant ruby errors... strange!
V2 now in the first post, right click (mouse over the knob) to centre the knob (when AutoCentre is disabled).
I'm still relatively new to this... Haven't learnt how to use the control keys yet.

Re: Configurable Joystick - X,Y Pad
Posted: Wed Dec 28, 2016 12:46 am
by RJHollins
The RUBY error is:
TypeError: (in method 'draw'): wrong argument type nil (expected DATA)
I can manually clear the error, but it comes back when re-loaded.
Re: Configurable Joystick - X,Y Pad
Posted: Thu Jan 05, 2017 12:33 pm
by DaveyBoy
Like I say I'm not getting any ruby errors here, I wonder if it's a version issue, I'm on v3.0.81.
Could try putting an afterload into a trigger input
