Skip to content
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

Slightly misleading "compatibility spec" #108

Closed
RoiEXLab opened this issue Sep 10, 2021 · 3 comments · Fixed by #111
Closed

Slightly misleading "compatibility spec" #108

RoiEXLab opened this issue Sep 10, 2021 · 3 comments · Fixed by #111

Comments

@RoiEXLab
Copy link

Hi everyone,
not sure if this is the right place to post this, but I thought I'd try anyways.
Basically I was browsing through available libraries for my nano every board, and noticed the "HID for megaavr" library, which explains how the library can be used for USB keyboard, mice, gamepads etc.
To my disappointement I got the "no native USB" error message from the macro, guess I'll have to buy another board for this then (even though technically the board has another USB chip on it that could in theory be used as well, but that's a different story).
I assume this compatibility information is derived from the architecture value specified here:


But I think this particular case shows that it needs to be a little bit more specific than that, especially for beginners this could be pretty misleading tricking them into thinking their board can do stuff that it clearly can't just to be greeted with a macro error.

TL;DR the HID library is displayed as "supported by nano every, Uno WiFi Rev2" in the arduino web IDE even though it clearly isn't supported, and I think this is misleading and should be fixed.

@facchinm
Copy link
Member

@arduino/ft_content

@per1234
Copy link
Contributor

per1234 commented Sep 13, 2021

@facchinm what is the purpose of the HID library in this repository?

@facchinm
Copy link
Member

Oh wow, none, it's just a leftover from the avr core legacy. We can safely remove it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants