| User | Post |
|
8:35 pm
May 3, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
I am using unbuntu 10.04 (fresh install) and mangler snapshot 1.1.20200227
however I am unable to set the mouse PTT, I can use the KB PTT with no issues
Everything else works fine with Mangler.
BTW love the program, does anyone have a suggestion as to where to look at fixing this?
|
|
|
8:39 pm
May 3, 2010
|
Haxar
| | |
| Moderator
| posts 58 |
|
|
Replace XInput2 with XInput1 and it should work just fine.
|
|
|
9:02 pm
May 3, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
Sorry for being newbish, but where would I find these files to change?
|
|
|
10:37 pm
May 3, 2010
|
econnell
| | |
| Admin
| posts 319 |
|
|
What do you mean you're unable to set it? Please give more information. Why can't you set it? What happens/doesn't happen?
|
|
|
10:44 pm
May 3, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
I have the "Enable Mouse Button Push to Talk" checked
Select Mouse is set to "Virtual core XTEST pointer
I then clicked the "Set" button and pressed my middle mouser (Wheel) button
When I try to use my middle mouse button it does not transmit.
|
|
|
10:45 pm
May 3, 2010
|
econnell
| | |
| Admin
| posts 319 |
|
|
So you can set it, and it doesn't work for PTT?
I'm guessing it is a logitech wireless mouse of some sort?
|
|
|
10:46 pm
May 3, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
|
10:53 pm
May 3, 2010
|
econnell
| | |
| Admin
| posts 319 |
|
|
This is a known issue with logitech wireless mice. The bug is really in xorg >= 1.7. The mouse slave device is not showing the button state when we query the master virtual pointer.
Not really sure how to work on this one yet. We may be able to update the code to xinput2 and query the slave device directly, but this is really something that needs to be fixed in xinput.
|
|
|
11:03 pm
May 3, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
Ok so long as you know the issue. I wasnt able to find much in my web searching about this issue.
Where can I look for more info about using the XInput1 that Haxar was talking about?
|
|
|
11:04 pm
May 3, 2010
|
econnell
| | |
| Admin
| posts 319 |
|
|
I don't think you can. Also, *I* know it's a known issue. I don't know if the xorg people are aware of it.
|
|
|
12:19 am
May 4, 2010
|
econnell
| | |
| Admin
| posts 319 |
|
|
Post edited 4:21 am – May 4, 2010 by ekilfoil
I spoke with the Ubuntu bug squad about this. First off, this is not Ubuntu specific. However, the Ubuntu people will ship this upstream when we report.
But I need someone experiencing this problem to file a bug in launchpad against the xinput package. You can do this by running:
$ ubuntu-bug xinput
Then I need to know the bug ID so I can add more information. Be sure to include your xinput device info in your bug report:
$ xinput list –long
Once I get the bug ID, I'll explain in more detail for them.
|
|
|
7:20 am
May 4, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
I will send you the info tonight.
Thank you for looking into this.
|
|
|
7:24 pm
May 4, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
Bug #575465
$ xinput list –long
unable to find device –long
|
|
|
7:35 pm
May 4, 2010
|
Haxar
| | |
| Moderator
| posts 58 |
|
|
Post edited 11:36 pm – May 4, 2010 by Haxar
It's:
xinput list ––long
|
|
|
7:48 pm
May 4, 2010
|
rigidknife
| | |
| Member | posts 8 |
|
|
⎡ Virtual core pointer id=2 [master pointer (3)]
Reporting 3 classes:
Class originated from: 9
Buttons supported: 24
Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right Button Side Button Extra Button Forward Button Back Button Task Button 8 Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown
Button state:
Class originated from: 9
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 9
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 1 units/m
Mode: relative
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 4
Buttons supported: 10
Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right None None None
Button state:
Class originated from: 4
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 4
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
⎜ ↳ Logitech USB Receiver id=9 [slave pointer (2)]
Reporting 4 classes:
Class originated from: 9
Buttons supported: 24
Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right Button Side Button Extra Button Forward Button Back Button Task Button 8 Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown Button Unknown
Button state:
Class originated from: 9
Keycodes supported: 248
Class originated from: 9
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 9
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 1 units/m
Mode: relative
⎜ ↳ Macintosh mouse button emulation id=10 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 10
Buttons supported: 5
Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down
Button state:
Class originated from: 10
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 1 units/m
Mode: relative
Class originated from: 10
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 1 units/m
Mode: relative
⎣ Virtual core keyboard id=3 [master keyboard (2)]
Reporting 1 classes:
Class originated from: 8
Keycodes supported: 248
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 5
Keycodes supported: 248
↳ Power Button id=6 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 6
Keycodes supported: 248
↳ Power Button id=7 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 7
Keycodes supported: 248
↳ Logitech USB Receiver id=8 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 8
Keycodes supported: 248
|
|
|
9:48 pm
May 4, 2010
|
econnell
| | |
| Admin
| posts 319 |
|
|
I didn't mean paste that info here. You need to open up a bug with Ubuntu and add this information to the ticket.
|
|
|
12:41 am
June 15, 2010
|
nvrpunk
| | |
| New Member | posts 1 |
|
|
I have the same issue, however, I am using btnx which I can get working with the wine+ventrilo (albeit only between windows in wine).
However, the button lists as Button10 when I use the Set option. I have tried setting btnx to match the button number it lists in the Xevent that it's apparently grabbing but this does not work as well.
I am sure there has to be a work around with btnx for just using mouse events. I can bind a key to a button and get it working however this triggers odd events in certain games.
|
|
Login 
Register 
Search 
Home
Print this Post 
Topic RSS 
