-
Notifications
You must be signed in to change notification settings - Fork 202
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
Add the Anyma, Eurolite and Fadecandy widgets. #543
Conversation
* along with this program; if not, write to the Free Software | ||
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. | ||
* | ||
* AnymauDMX.cpp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Firstly, personally I'm still in favour of the files just being manufacturer, rather than manufacturer-device.
Regardless of that, this file doesn't match the Camel Case style we're using elsewhere, and just looks a bit odd to me. I wonder if it should be AnymaUDmx.cpp?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The actual name of the device is uDMX.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, but we don't stick to that with include/ola/DmxBuffer.h; although we're not very consistent looking at include/ola/http/HTTPServer.h.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I standardized on 'DMX' for the client code but DmxBuffer predates that. I'd prefer to use DMX going forward.
Looks good aside from comments. I need to test that your Fadecandy code works. |
Add the Anyma, Eurolite and Fadecandy widgets.
No description provided.