Timeline for Writing a class to hold Arduino Properties for an Arduino I2C Debugger
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2015 at 13:22 | comment | added | fr00z1 | Sorry for the late reply, haven't logged in for a while. You are 100% correct on @property. Miss on my part. I blame lack of sleep.. :-) Your reasons on the other methods may be valid as well, however the potential confusion (imho) is the method names will need a double take as camelCase is a convention typically reserved for class names (or if following an existing convention). If I were looking at your code for the 1st time, I most likely would miss the arduino lib correlation. pep8 (See class/method/function conventions) | |
| Jul 20, 2015 at 13:09 | comment | added | sawyermclane |
For the functions where you say change them to "get_id" or something along those lines, I thought that when creating an attribute with the @property decorator, the method name had to be the name of the intended attribute. Also for the serialCommand and connectPort methods, they're meant to shadow existing commands in the ArduinoI2C library, so an ARCArduino object can be used similarly to an ArduinoI2C object.
|
|
| Jul 18, 2015 at 23:19 | history | answered | fr00z1 | CC BY-SA 3.0 |