-
-
Notifications
You must be signed in to change notification settings - Fork 7k
Solution for: Leonardo keyboard API only allows ASCII input #1391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…s Keyboard_ to fix issues with the QWERTY-only press(k) and release(k) methods. Additionally rewrite press(k) and release(k) to actually use the new *Keycode(k, send) methods and add some KEYCODE_* defines.
…ontained in the fix for issue arduino#1391 and the code was redundant
As I'm reviewing HID-related commits, I notice that you did a lot of rewriting of 0 to 0x00 and 1 to 0x01. Is this anything other than just a personal preference? |
This is just a personal preference. |
On 10.01.2014, at 01:14, Jesse Vincent [email protected] wrote:
Just a personal preference, I’m always using hex values for bitmasks and decimal values for bit numbers. For 0 and 1 this makes no big difference but for 0x1000 it is better readable. Michael |
nod Thanks, guys. One of the things I'm doing is splitting up the HID-related pull requests into one logical change per commit and extracting diffs that are just whitespace/cosmetic changes from the actual functional changes. That'll make it easier for the folks with commit privileges to review and explicitly accept or reject changes, rather than have them hang out as pull requests. Thank you both for the work you've done on this stuff. I've been using it locally. I'm hoping to have a branch with the work on pull request 1391 and pull request 1488 ready for review in the next week or so. |
@obra, sounds like a great plan, thanks! |
Is there any word on when this might make it into an Arduino IDE release? |
On Tue, Feb 11, 2014 at 10:04:19AM -0800, rokison wrote:
I'm hard at work on it. Right now, it adds way too much overhead to arduino sketches that don't use the new functionality. I'd actually appreciate it if folks would test my code before it makes it into an IDE release. If you're up for building the IDE with these changes and trying them, that'd be double-plus amazing. |
I am quite a novice when it comes to building an IDE (in that I’ve never done it), but I’m more than willing to give it a try. From: Jesse Vincent [mailto:[email protected]] On Tue, Feb 11, 2014 at 10:04:19AM -0800, rokison wrote:
I'm hard at work on it. Right now, it adds way too much overhead to arduino sketches that don't use the new functionality. I'd actually appreciate it if folks would test my code before it makes it into an IDE release. If you're up for building the IDE with these changes and trying them, that'd be double-plus amazing. — St Paul's School is a charitable company limited by guarantee registered in England at ##################################################################################### |
On Tue, Feb 11, 2014 at 10:27:47AM -0800, rokison wrote:
Excellent. The easiest thing to do is to git clone my fork with the branch for the new code. git clone https://github.com/obra/arduino
That might make a good Library on top of the core functionality. (Which would also let it iterate faster than the IDE)
|
Close with #1803 |
Add pressKeycode(k, send) and releaseKeycode(k, send) methods to class Keyboard_ to fix issues with the QWERTY-only press(k) and release(k) methods. Additionally rewrite press(k) and release(k) to actually use the new Keycode(k, send) methods and add some KEYCODE_ defines.
This fixes the following issue: #1386