Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences here.
×
×
Cookie Preferences
We use Cookies to help personalize and improve Roll20. For more information on our use of non-essential Cookies, visit our Privacy Policy here.
Good point about the keylogging - though if keylog events were only registered when there was a "focus" on the roll20 window (thus not for instance in Skype of entering a password elsewhere, for instance) that danger could potentially be bypassed, no? That said, you might be right as to the security risk of that generally. But arrow key events would be brilliant.
I would instead prefer it if we could just put events on specific keys, such as F1-F12, arrow keys, 1-0. Perhaps tie a macro to that key, and then we could assign the API script to the macro, etc
+1 to event logging very VERY specific keys. Macros probably wouldn't be the way to go I dont think though. Probably just have it send an API event if API is spun && selection isn't on the chat box.
