Timeline for How to force the user to comply with a command?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 22, 2016 at 20:10 | history | bounty ended | shackra | ||
| S Oct 22, 2016 at 20:10 | history | notice removed | shackra | ||
| Oct 20, 2016 at 16:22 | vote | accept | shackra | ||
| Oct 20, 2016 at 10:02 | answer | added | clemera | timeline score: 2 | |
| Oct 18, 2016 at 14:05 | comment | added | Tobias |
You know the command for the single keystroke, you know the command for the key sequence, and you know the requirements on the user input for both commands. Just check the requirements for the key sequence in your functions. You could even write per-function advices or rebind the keys such that the wrong user-input is gobbled. If you want to keep your construction you could add that information in some form to schrute-shortcuts-commands.
|
|
| S Oct 15, 2016 at 20:45 | history | bounty started | shackra | ||
| S Oct 15, 2016 at 20:45 | history | notice added | shackra | Draw attention | |
| Oct 13, 2016 at 13:49 | history | edited | Drew | CC BY-SA 3.0 |
added 53 characters in body; edited tags
|
| Oct 13, 2016 at 6:58 | history | asked | shackra | CC BY-SA 3.0 |