Louis Pontoise
339aeaabe6
* user was able to set a nextWindowShortcut which contained modifiers from holdShortcut * detection of conflicts was incorrect in some cases, mostly because holdShortcut and nextWindowShortcut should be treated as 1 shortcut * after the user forces a shortcut to apply, resetting the existing one with the same keys, it wouldn't save to UserDefaults * forcing the holdShortcut to replace another holdShortcut would reset it, even though holdShortcut should always be set with some value
