You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not my first time round here, previously made #27, but I'm here for something different today. I was wondering if it would be possible to add functionality to configure custom keyboard shortcuts? Since we have an ini file, I believe this would be easy enough if we follow a key naming convention, along with keys that effectively disable a specific shortcut (e.g. xkill, something I don't use). I'd much rather prefer to use WIN+ALT+F4 for force kill foreground window instead of CTRL+ALT+F4, as less applications watch the keys pressed once the Windows key has been pressed, at least from experience.
Thanks,
Elliott
The text was updated successfully, but these errors were encountered:
Please allow custom keys, I had SuperF4 autolaunch on startup, but I found out it conflicts with another program I use Ctrl+alt+F4 with and I couldn't figure out why my programs would close when I hit the combination (Program would chain clicks together for repetitive tasks, but superF4 would kill the program instead)
Custom hotkeys would be good, but in the meantime, you can use another hotkey/macro program to compensate. For example, you could use the following AutoHotkey script to customize your usage, replacing the window title and hotkey as needed:
; make ⊞Win+Q kill Notepad
#IfWinActive, Notepad
#q::send ^!{f4}
Hey there,
Not my first time round here, previously made #27, but I'm here for something different today. I was wondering if it would be possible to add functionality to configure custom keyboard shortcuts? Since we have an ini file, I believe this would be easy enough if we follow a key naming convention, along with keys that effectively disable a specific shortcut (e.g. xkill, something I don't use). I'd much rather prefer to use WIN+ALT+F4 for force kill foreground window instead of CTRL+ALT+F4, as less applications watch the keys pressed once the Windows key has been pressed, at least from experience.
Thanks,
Elliott
The text was updated successfully, but these errors were encountered: