QDNX Bug Tracker :: QDNX Bug Tracker :: RatSlap: Recently edited tasks https://bugs.qdnx.org/ 2018-08-06T15:19:17Z QB#119: Unrecognised keys/buttons fail silently 2018-08-06T15:19:17Z 2017-04-12T06:05:10Z

QB#118 shows that unrecognised parameters (such as “button5”) fail silently,
assigning 000000h instead of reporting an error.

Krayon https://bugs.qdnx.org/:119
QB#118: Button5 cannot be assigned to G5 2018-08-06T15:16:03Z 2017-04-12T05:52:24Z

From GitHub Issue #9 by adrfantini:

I have a very weird behaviour here. After having modified many buttons to
suit my needs, I have the following problem.

I cannot assign many software mouse Buttons to many hardware buttons.
Assigning keys seems to always work tho.

Say I am in this situation:
...
  sudo ratslap --p F3
  Left Click (But1):   Button1
  Right Click (But2):  Button2
  Middle Click (But3): Button3
  G4:                  
  G5:                  
  G6:                  
  G7:                  
  G8:                  ModeSwitch
  G9:                  DPICycle
...
Now let's try to modify it with:
  sudo ratslap --modify F3 --G4 Button4
Result:
  sudo ratslap --p F3
  Left Click (But1):   Button1
  Right Click (But2):  Button2
  Middle Click (But3): Button3
  G4:                  
  G5:                  
  G6:                  
  G7:                  
  G8:                  ModeSwitch
  G9:                  DPICycle
Nothing! Let's try assigning keys instead:
  sudo ratslap --modify F3 --G4 LeftAlt+K
  Left Click (But1):   Button1
  Right Click (But2):  Button2
  Middle Click (But3): Button3
  G4:                  LeftAlt + K
  G5:                  
  G6:                  
  G7:                  
  G8:                  ModeSwitch
  G9:                  DPICycle
Works...

In short, I can seem to bind mouse Buttons anymore!

However, some, like sudo ratslap --modify F3 --G7 Button9 work, while others,
like sudo ratslap --modify F3 --G7 Button5 do not.
Krayon https://bugs.qdnx.org/:118
QB#116: Modes should have simpler names such as A, B, C 2018-08-06T15:14:55Z 2016-11-17T11:15:14Z

The mode names should be simpler than “F3”, “F4” and “F5”. They were only named
this way as that was the hex code for the mode, hardly user friendly.

Krayon https://bugs.qdnx.org/:116
QB#115: Ability to save/load profiles 2018-08-06T15:14:40Z 2016-11-09T11:45:46Z

Would be nice to be able to save and load profiles.

Krayon https://bugs.qdnx.org/:115
QB#112: Distribution package should contain arch 2018-08-06T15:14:05Z 2016-11-08T22:30:50Z

The built dist package is named “ratslap-0.2.0.tar.gz” regardless of architecture.

Krayon https://bugs.qdnx.org/:112
QB#125: Error assigning Num+ 2018-08-06T15:13:33Z 2018-07-22T16:59:56Z

From GitHub Issue #16 by vdomos :

  Hi,
  
  I have this error when assign a button to LeftCtrl+Num+ (zoom+ in FIrefox),
  LeftCtrl+Num- is ok.
  
      $ ./ratslap --modify F3 --G7 LeftCtrl+Num+ --G6 LeftCtrl+Num- --print F3 --select F3                  
      RatSlap v0.2.2-tags/0.2.2^0 (BUILT: 2018-07-11 11:06:16+0200)
      Copyright (C) 2016 Todd Harbour
      Linux configuration tool for Logitech mice (currently only G300/G300S)
      https://gitlab.com/krayon/ratslap/
      Found Logitech G300s (046d:c246) @ 0x5568a0d53ce0
      Detaching kernel driver...
      Modifying Mode: F3
          Setting button 7: LeftCtrl+Num+
      20180712T132246+0200 [E]           main.c:01101:set_mode_button ERROR: Invalid modifier (Num) specified: LeftCtrl+Num+
          Setting button 6: LeftCtrl+Num-
      Saving Mode: F3
      Printing Mode: F3
        Colour:              cyan
        Report Rate:          500
        DPI #1:               500
        DPI #2:        (DEF) 1000
        DPI #3:              1500
        DPI #4:              2500
        DPI Shift:           NOT SET
        Left Click (But1):   Button1
        Right Click (But2):  Button2
        Middle Click (But3): Button3
        G4:                  Button6
        G5:                  Button7
        G6:                  LeftCtrl + Num-
        G7:                  Button9
        G8:                  LeftCtrl + Tab
        G9:                  LeftCtrl + LeftShift + Tab
      Mode Selection Specified: F3
      Selecting Mode: F3
      Attaching kernel driver...
Krayon https://bugs.qdnx.org/:125
QB#124: Failed operations don't abort execution 2018-08-06T15:11:53Z 2018-07-10T15:32:34Z

A failed operation doesn’t abort execution such that subsequent parameters are
still parsed and executed. eg.

$ ./ratslap -s INVALID1 -s INVALID2 -s INVALID3
RatSlap v0.2.2 (BUILT: 2018-05-01 01:00:50+1000)
Copyright (C) 2016 Todd Harbour
Linux configuration tool for Logitech mice (currently only G300/G300S)
https://gitlab.com/krayon/ratslap/
Found Logitech G300s (046d:c246) @ 0x1470620
Detaching kernel driver...
20180711T012738+1000 [E]           main.c:01322:main            ERROR: Invalid mode for select option: INVALID1
20180711T012738+1000 [E]           main.c:01322:main            ERROR: Invalid mode for select option: INVALID2
20180711T012738+1000 [E]           main.c:01322:main            ERROR: Invalid mode for select option: INVALID3
Attaching kernel driver...

I can’t think of any way at present that this could be bad but it’s probably
not a good idea.

Krayon https://bugs.qdnx.org/:124
QB#123: Check mode_load() return code 2018-08-06T15:11:40Z 2018-07-10T14:23:31Z

Currently we are not checking the return code of mode_load(). This could lead
to weird results in the printing of a mode.

Krayon https://bugs.qdnx.org/:123
QB#122: Help shouldn't require USB permissions 2018-08-06T15:11:27Z 2018-07-08T07:43:04Z

From GitHub Issue #15 by ChillyWillyGuru:

If you run 'ratslap -h' normally such that the user doesn't have access to
the usb, you get an error about not being able to do any usb ops rather than
the help. Help should ALWAYS be available. I'd suggest checking if the help
option has been asked for first before anything else, and if so print the
help and exit. Only if the user doesn't want help should it then try to get
the usb.
Krayon https://bugs.qdnx.org/:122
QB#107: Reset to defaults/factory reset option 2018-07-10T14:45:13Z 2016-11-08T13:35:57Z

At present, the original configuration is lost once you modify the modes of the
mouse. An option to return the mouse to it’s factory defaults would be
advantageous.

Krayon https://bugs.qdnx.org/:107