Existing config file issues: comment blocks are parsed instead of ignored, editor seemingly removes mouse_buttons

[Squaredude]

Hi! I just gave this a try, and ran into a couple of bugs.

First one, it seems it can't handle comments (lines starting with #). It told me there were syntax errors within commented lines. After removing those lines, the config loaded.

The second one, is that all the mouse_buttons got removed from the stroke gestures. And after trying the config saved by the editor, it seemed to default to any button or the left-click one (it was quite erratic). But even when I set a button to be used within the editor, it wasn't taken into account by Input Actions, so there seems to be an issue there, as well.

All in all, the editor is working really well for being this new. I was happy to see my strokes visualized.

Cheers!

[Luwx]

Can you send here the config with line comments and the one that was not recognized by input actions?

[Squaredude]

This block is something I copied from someone else, and I kept it at the top of my config file for reference as I learn how to set different things in YAML.

#device_rules:
#  - conditions:
#      all:
#        - any: # remove some conditions if you don't use triggers for a specific device type
#          - $types contains keyboard # keyboards must be grabbed for Trigger.clear_modifiers to work
#          - $types contains mouse # ungrabbed mice are currently very buggy
#          - $types contains touchpad # touchpad event filtering is experimental and may cause issues
#        - not: # blacklist
#          - $name == Yubico YubiKey OTP+FIDO+CCID
#    grab: true
#    ignore: false
#
#  - conditions: $types != keyboard
#    ignore: true # ignore all devices other than keyboards (required to get modifiers) by default

#mouse:
#  gestures:
#    - type: stroke
#      strokes: [ 'N2QAyywAZAA=' ]
#      mouse_buttons: [ extra1 ] # comment
##      mouse_buttons: [ extra1 ] # comment
#
#      actions:
#        - on: begin
#          input:
#            - keyboard: [ a ]

I got the error alert on the third-to-last line (- on: begin, which I don't use anywhere in my config). So it seems to be parsing commented-out lines.

The generated config I discarded it, so I can't provide it. But I read a conversation you had in the InputActions repo, where it was said your program is better used to generate a brand new config file rather than use an old one made by hand. I was using the old config file, basically, so maybe it's not a useful report for you. (Feel free to close or dismiss the issue, if so.)

I'll see if I can try again this Monday, starting a config off from scratch.

[Squaredude]

Sorry for the delay! I'm slowly recreating the config solely through your program, and it's working really well when beginning with a completely empty file. So, I'm closing this issue, since I feel it would be a waste of time to try to deal with existing configs. It's better to tell people to recreate it with the UI, imo.

I'm having an unrelated problem with the UI. Not sure if you want me to open a new issue, for this. On a 2160p screen, the text is hard to read. Everything works fine, it's just me not seeing well. I'm able to solve it somewhat with KDE's accessibility settings, the zoom stuff in particular is very helpful.