dc0337d2e5
With example config:
mode "a_mode" {
bindcode 27 --release mode "default"
}
bindsym $mod+r mode "a_mode"
The first time $mod+r is pressed "a_mode" is activated like normal. When
r (bindcode 27) is pressed to exit the mode:
- On the KeyPress event the corresponding bind->release is correctly
marked as B_UPON_KEYRELEASE_IGNORE_MODS.
- On the KeyRelease event the command 'mode "default"' is executed but
bind->release is still B_UPON_KEYRELEASE_IGNORE_MODS since they are only
reset on KeyPress events.
The second time $mod+r is pressed and "a_mode" is activated and when the
r key is released the 'mode "default"' is executed even though the mods
are not matching since bind->release == B_UPON_KEYRELEASE_IGNORE_MODS.
This still doesn't catch 2 cases:
1. When the order is: press $mod -> press r -> release $mod -> release
r. Since 'r' is released without any modifiers the binding matches.
2. With:
mode "resize" {
bindsym --release r mode "default"
}
bindsym r mode "resize"
This is arguably correct: on the KeyPress event we switch to the mode and
on the KeyRelease we switch back.
|
||
|---|---|---|
| .github | ||
| AnyEvent-I3 | ||
| contrib | ||
| debian | ||
| docs | ||
| etc | ||
| i3-config-wizard | ||
| i3-dump-log | ||
| i3-input | ||
| i3-msg | ||
| i3-nagbar | ||
| i3bar | ||
| include | ||
| libi3 | ||
| m4 | ||
| man | ||
| parser-specs | ||
| share | ||
| src | ||
| testcases | ||
| travis | ||
| .clang-format | ||
| .editorconfig | ||
| .gitignore | ||
| .travis.yml | ||
| DEPENDS | ||
| I3_VERSION | ||
| LICENSE | ||
| Makefile.am | ||
| PACKAGE-MAINTAINER | ||
| README.md | ||
| RELEASE-NOTES-4.15 | ||
| configure.ac | ||
| generate-command-parser.pl | ||
| i3-dmenu-desktop | ||
| i3-migrate-config-to-v4 | ||
| i3-save-tree | ||
| i3-sensible-editor | ||
| i3-sensible-pager | ||
| i3-sensible-terminal | ||
| logo.svg | ||
| pseudo-doc.doxygen | ||
| release.sh | ||
README.md
i3: A tiling window manager
i3 is a tiling window manager for X11.
For more information about i3, please see the project's website and online documentation.
For information about contributing to i3, please see CONTRIBUTING.md.