David Lechner
David Lechner
The current lego-sensor class does not know about strings. In other words, `valueX` can't return text. The way I was envisioning it is that if you want to read the...
It will write the table to `bin_data`. My thinking is that you just copy the `value` fields from `struct input_event` to an array and that is what you write to...
Minor point: Since the device path is `/dev/input/eventX`, why not call it `event2sensor`. `evdev` is just too similar to `ev3dev`. Also, using "2" instead of "to" is also fairly common,...
Have a look at `/sys/class/input/event0/device/capabilities/`. This enumerates what keys/axis/etc. are available. There are also ioctls that do the same thing, which might be better since they put the data in...
There is a json file for sensor definitions, so you could automatically generate classes for each specific type of sensor. For the various subsystems though, only half of what you...
There is an existing JSON file for motors, but as I think I have mentioned before, it is currently maintained by hand. And also, like the sensors, this is just...
This is an interesting idea. I will have to think about it for a while (both the specific change and the bigger future of ev3dev in general).
Rather than making platform specific power supplies, I would suggest utilizing the `scope` attribute (same as the `POWER_SUPPLY_SCOPE` property) to find the "System" power supply.
Yes, that is what I mean. Just a suggestion.
I think that sounds good. I would like the same program to run on any platform without having to make any changes.