Ralph Hempel

Motor movement is non blocking but there is a callback mechanism that tells you if the command was interrupted by another one, or the motor stalled, or the motion completed....

Am I missing something? Don't we just need to change ''' DEVICE_ROOT_PATH = '/sys/class' ''' In 'core.py'

I think this is a good idea - so are you suggesting something in `spec.json` - an entry for each `binding` with: - language - package name - repo location...

Ack that will make it into the next spin of the module - we'll be adding the static button state hopefully :-)

Welcome to the club Juan Antonio - I think you will like this project and we look forward to your contributions on the Java binding.

Well, the LCD needs IOCTLs now, but maybe we can fix that :-) Right now the Python API has a nice [ButtonBase class](https://github.com/rhempel/ev3dev-lang-python/blob/master/ev3dev/core.py#L1806) that is extended to handle the remote...

I am trying to make things as easy as possible for people getting into coding that don't think about event based frameworks as easily as "just give me a function...

Yes, something like that could work - seems a bit roundabout but it's doable. Another option is to have a kernel module specifically for the EV3 buttons that does not...

I was doing some reading and I think that a userland program that uses `libev3dev` is the way to go - it does not interfere with the ability to do...

I mean libevdev :-)