Thread: [Tuxpaint-devel] Joystick support
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Pere P. i C. <per...@gm...> - 2011-05-28 10:40:47
|
Hi all! I've just improved the support for painting with a joystick, Can somebody test? Specially I am interested in the ball motion as my joystick hasn't a ball. Also, I am interested too if the defaults values are good, now they are the same as Ankit left in GSOC, in my joystick they work right, but the 3200 low motion treshold seems too high, but I think too that used joysticks may trigger unwanted motion events. Also the default slowness is adapted to my box, so it should be tested too. commandline: --joystick-slowness 0-500 default 15 --joystick-threshold 0-32766 default 3200 --joystick-maxsteps 0-7 default 7 Thanks Pere |
From: Bill K. <nb...@so...> - 2011-05-28 17:33:17
|
On Sat, May 28, 2011 at 12:40:36PM +0200, Pere Pujal i Carabantes wrote: > Hi all! > > I've just improved the support for painting with a joystick, Can > somebody test? Thanks Pere, very exciting! I just tested with a Sony PlayStation 2 control pad, connected to my laptop's USB via an older (original PlayStation era) adapter. The analog control worked fine. Pressing any button acts as clicking (X, O, square, triangle, the L1, L2, R1 and R2 shoulder buttons, Select, Start, and even pushing in on the analog controller -- though that I only noticed accidentally. Options to fine-tune would be nice. And maybe even connect some buttons to keypresses... e.g., L1 for ^Z undo, R1 for ^R redo? :) ) The digital control worked, but only moves the mouse pointer one pixel in any direction. (So I need to release, and press again, to move it another pixel, etc.) I have a Stelladapter, which lets me use Atari 2600 (Commodore 64, etc.) joysticks on my PC, but it's hiding somewhere in a closet. (Ironically, there are two Atari joysticks sitting on the counter next to me. ;) ) > Specially I am interested in the ball motion as my joystick hasn't a > ball. I don't have a "real PC joystick", and honestly, I'm not even sure what a ball is. (I _think_ I know what a hat is. :) ) > Also, I am interested too if the defaults values are good, now they are > the same as Ankit left in GSOC, in my joystick they work right, but the > 3200 low motion treshold seems too high, but I think too that used > joysticks may trigger unwanted motion events. I tried with the defaults, and it worked fine. This kind of thing will probably require a lot of testing and feedback from a much larger collection of people than even just us developers. (How often do I use any kind of "joystick" with my own PC? Basically never!) OTOH, I think I can track down a few folks who use Tux Paint with physically disabled users, who have been wanting joystick functionality... I can see if they can help beta test, if we can get builds made for them. > Also the default slowness is adapted to my box, so it should be tested > too. > > commandline: > --joystick-slowness 0-500 default 15 > --joystick-threshold 0-32766 default 3200 > --joystick-maxsteps 0-7 default 7 PS - I see you edited OPTIONS.txt. You should edit html/OPTIONS.html, and then run "make" in the "docs/" directory to regenerate the TXT version. (It invokes "links" browser with "-dump" option, and redirect's (>) the output to the TXT file.) Other docs that are HTML based (and TXT is generated) are: ADVANCED-STAMPS-HOWTO EXTENDING README FAQ Oh, and I also added the options to the man page (src/manpage/tuxpaint.1) Thanks!!! -bill! |
From: Pere P. i C. <per...@gm...> - 2011-05-28 22:11:12
|
El ds 28 de 05 de 2011 a les 10:33 -0700, en/na Bill Kendrick va escriure: > On Sat, May 28, 2011 at 12:40:36PM +0200, Pere Pujal i Carabantes wrote: > > Hi all! > > > > I've just improved the support for painting with a joystick, Can > > somebody test? > > Thanks Pere, very exciting! I just tested with a Sony PlayStation 2 > control pad, connected to my laptop's USB via an older (original PlayStation > era) adapter. > > The analog control worked fine. Pressing any button acts as clicking > (X, O, square, triangle, the L1, L2, R1 and R2 shoulder buttons, > Select, Start, and even pushing in on the analog controller -- though that > I only noticed accidentally. Options to fine-tune would be nice. > And maybe even connect some buttons to keypresses... e.g., L1 for ^Z undo, > R1 for ^R redo? :) ) It detects ANY button and sends a mouse button event, this is in purpose. Are there a mapping from L1, R1... to SDL button 0, button 1... ? If different devices does different mappings, then we will go into trouble. And, in any case, which buttons should be mapped to which actions? > The digital control worked, but only moves the mouse pointer one pixel > in any direction. (So I need to release, and press again, to move it > another pixel, etc.) So it is detected by SDL as a Hat, it does move just a pixel on purpose, to allow more precition when placing the pointer, do you think this must be changed? > > > I have a Stelladapter, which lets me use Atari 2600 (Commodore 64, etc.) > joysticks on my PC, but it's hiding somewhere in a closet. (Ironically, > there are two Atari joysticks sitting on the counter next to me. ;) ) > > > > Specially I am interested in the ball motion as my joystick hasn't a > > ball. > > I don't have a "real PC joystick", and honestly, I'm not even sure what > a ball is. (I _think_ I know what a hat is. :) ) I had to buy a joystick to mentor last year, now it is full of dust ;) I "supose" that a ball is something similar to the trackball devices from some times ago. > > Also, I am interested too if the defaults values are good, now they are > > the same as Ankit left in GSOC, in my joystick they work right, but the > > 3200 low motion treshold seems too high, but I think too that used > > joysticks may trigger unwanted motion events. > > I tried with the defaults, and it worked fine. This kind of thing will > probably require a lot of testing and feedback from a much larger > collection of people than even just us developers. (How often do I use > any kind of "joystick" with my own PC? Basically never!) > > OTOH, I think I can track down a few folks who use Tux Paint with > physically disabled users, who have been wanting joystick functionality... > I can see if they can help beta test, if we can get builds made for them. > > > > Also the default slowness is adapted to my box, so it should be tested > > too. > > > > commandline: > > --joystick-slowness 0-500 default 15 > > --joystick-threshold 0-32766 default 3200 > > --joystick-maxsteps 0-7 default 7 > > PS - I see you edited OPTIONS.txt. You should edit html/OPTIONS.html, > and then run "make" in the "docs/" directory to regenerate the TXT version. > (It invokes "links" browser with "-dump" option, and redirect's (>) the > output to the TXT file.) > > Other docs that are HTML based (and TXT is generated) are: > > ADVANCED-STAMPS-HOWTO > EXTENDING > README > FAQ > > Oh, and I also added the options to the man page (src/manpage/tuxpaint.1) Oh, OK, nice to know :) Thanks Pere |
From: John P. <jo...@jo...> - 2011-06-28 02:32:32
|
Hi, it's me John, I've changed my email address. I can confirm that the latest CVS version has joystick support that works on Windows :-) best regards, John. PS I had to dig out my 'Gamepad' thingy to test it. On Sat, May 28, 2011 at 12:40:36PM +0200, Pere Pujal i Carabantes wrote: > Hi all! > > I've just improved the support for painting with a joystick, Can > somebody test? > > Specially I am interested in the ball motion as my joystick hasn't a > ball. > > Also, I am interested too if the defaults values are good, now they are > the same as Ankit left in GSOC, in my joystick they work right, but the > 3200 low motion treshold seems too high, but I think too that used > joysticks may trigger unwanted motion events. > > Also the default slowness is adapted to my box, so it should be tested > too. > > commandline: > --joystick-slowness 0-500 default 15 > --joystick-threshold 0-32766 default 3200 > --joystick-maxsteps 0-7 default 7 > > > Thanks > Pere > > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > Tuxpaint-devel mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel |
From: Bill K. <nb...@so...> - 2011-07-02 08:05:34
|
On Sun, May 29, 2011 at 12:11:01AM +0200, Pere Pujal i Carabantes wrote: > It detects ANY button and sends a mouse button event, this is in > purpose. > Are there a mapping from L1, R1... to SDL button 0, button 1... ? > If different devices does different mappings, then we will go into > trouble. Well, this is where it'd be nice to have some way of configuring it, but we can deal with that later. Anything is better than nothing. :) We can iterate the functionality improvements as time (and releases) goes on. > And, in any case, which buttons should be mapped to which actions? > > > The digital control worked, but only moves the mouse pointer one pixel > > in any direction. (So I need to release, and press again, to move it > > another pixel, etc.) > > So it is detected by SDL as a Hat, it does move just a pixel on purpose, > to allow more precition when placing the pointer, do you think this must > be changed? Oh, no. Good to understand why it acted like that. ;) <snip> Thanks again for integrating/implementing this! -- -bill! Sent from my computer |
From: Pere P. i C. <per...@gm...> - 2011-07-02 22:23:07
|
El ds 02 de 07 de 2011 a les 01:05 -0700, en/na Bill Kendrick va escriure: > On Sun, May 29, 2011 at 12:11:01AM +0200, Pere Pujal i Carabantes wrote: > > It detects ANY button and sends a mouse button event, this is in > > purpose. > > Are there a mapping from L1, R1... to SDL button 0, button 1... ? > > If different devices does different mappings, then we will go into > > trouble. > > Well, this is where it'd be nice to have some way of configuring it, but > we can deal with that later. Anything is better than nothing. :) > We can iterate the functionality improvements as time (and releases) goes on. I will se what I can do about this... > > > > > The digital control worked, but only moves the mouse pointer one pixel > > > in any direction. (So I need to release, and press again, to move it > > > another pixel, etc.) > > > > So it is detected by SDL as a Hat, it does move just a pixel on purpose, > > to allow more precition when placing the pointer, do you think this must > > be changed? > > Oh, no. Good to understand why it acted like that. ;) I am just thinking that it could act like the keyboard does, a key press when pressed, then a timeout, then repeat the holded key. Will see if we can apply to a Hat, like: a motion of 1 pixel when pushed, then a configurable timeout,say one or two seconds, then repeated motions of 1 pixel at a configurable interval. Thanks Pere P.S. Some time ago I've lost fornol.no-ip.org due to a forgot of renewal, so pe...@fo... is no more valid. |
From: Pere P. i C. <per...@gm...> - 2011-07-31 14:31:09
|
Forgot to send this to the list, replied only to me XD El dg 03 de 07 de 2011 a les 00:22 +0200, en/na Pere Pujal i Carabantes va escriure: > El ds 02 de 07 de 2011 a les 01:05 -0700, en/na Bill Kendrick va > escriure: > > Well, this is where it'd be nice to have some way of configuring it, but > > we can deal with that later. Anything is better than nothing. :) > > We can iterate the functionality improvements as time (and releases) goes on. > > I will se what I can do about this... For now there are shortcurts to the main tools on the left, as well as "page setup" and "escape" that is more useful than "quit". Perhaps would be useful too two shortcurts to the scroll buttons on the right? I can't imagine good defaults, so they are disabled for now, well, they aren't strictly disabled, they are set to 255 but I hardly imagine a joystick with 256 buttons. Command line values allowed from 0 to 254, defaults to 255. The value should be the button number (as seen by SDL) that we want to associate to the action. joystick-btn-escape, sends a escape event, for dismiss dialogs and quit joystick-btn-brush, selects the brush tool by sending a mouse click event over the button joystick-btn-stamp, selects the stamp tool " joystick-btn-lines, selects the lines tool " joystick-btn-shapes, " joystick-btn-text, " joystick-btn-label, " joystick-btn-magic, " joystick-btn-undo, sends a CTRL z event joystick-btn-redo, sends a CTRL r event joystick-btn-eraser, selects the eraser tool joystick-btn-new, sends a CTRL n event joystick-btn-open, a CTRL o event joystick-btn-save, CTRL s joystick-btn-pgsetup, CTRL SHIFT p. What is page setup meant to do? I my box only raises the print dialog. joystick-btn-print, CTRL p [speaking of a hat] > I am just thinking that it could act like the keyboard does, a key press > when pressed, then a timeout, then repeat the holded key. Will see if we > can apply to a Hat, like: > a motion of 1 pixel when pushed, then a configurable timeout,say one or > two seconds, then repeated motions of 1 pixel at a configurable > interval. > In CVS :) Commandline: --joystick-hat-slowness, Adds a SDL_Delay of the value at each move after the timeout. Default 15 (0.15s), allowed from 0 to 500 --joystick-hat-timeout, the lapse between the first move and the following serie of moves. Default 1000 (1s), allowed from 0 to 3000 Could somebody update the docs, please? This would save me a lot of time :) Thanks Pere El dg 03 de 07 de 2011 a les 00:22 +0200, en/na Pere Pujal i Carabantes va escriure: > El ds 02 de 07 de 2011 a les 01:05 -0700, en/na Bill Kendrick va > escriure: > > On Sun, May 29, 2011 at 12:11:01AM +0200, Pere Pujal i Carabantes wrote: > > > It detects ANY button and sends a mouse button event, this is in > > > purpose. > > > Are there a mapping from L1, R1... to SDL button 0, button 1... ? > > > If different devices does different mappings, then we will go into > > > trouble. > > > > Well, this is where it'd be nice to have some way of configuring it, but > > we can deal with that later. Anything is better than nothing. :) > > We can iterate the functionality improvements as time (and releases) goes on. > > I will se what I can do about this... > > > > > > > > The digital control worked, but only moves the mouse pointer one pixel > > > > in any direction. (So I need to release, and press again, to move it > > > > another pixel, etc.) > > > > > > So it is detected by SDL as a Hat, it does move just a pixel on purpose, > > > to allow more precition when placing the pointer, do you think this must > > > be changed? > > > > Oh, no. Good to understand why it acted like that. ;) > > I am just thinking that it could act like the keyboard does, a key press > when pressed, then a timeout, then repeat the holded key. Will see if we > can apply to a Hat, like: > a motion of 1 pixel when pushed, then a configurable timeout,say one or > two seconds, then repeated motions of 1 pixel at a configurable > interval. > > > Thanks > Pere > > P.S. > Some time ago I've lost fornol.no-ip.org due to a forgot of renewal, so > pe...@fo... is no more valid. > > |