Stopping/stop commands usability (C++) about ev3dev-lang HOT 5 CLOSED

I think this is not just C++. The bindings are using uniform specification, so any changes in the attribute names should be done by @dlech in ev3dev/lego-linux-drivers first.

Also, I think the docs at http://www.ev3dev.org/docs/drivers/tacho-motor-class/ are quite clear on this subject. Do you have any specific changes in mind?

from ev3dev-lang.

@WasabiFan, on a slightly related note, I am thinking of manually copying documentation strings from comments in ev3dev/lego-linux-drivers into spec.json structure. I would then use those to generate comments for C++ bindings and docstrings for python. Would you mind against this?

from ev3dev-lang.

I am thinking of manually copying documentation strings from comments in ev3dev/lego-linux-drivers into spec.json structure. I would then use those to generate comments for C++ bindings and docstrings for python. Would you mind against this?

Nope; this is exactly what I was hoping for in adding the "description" fields in some of the objects. You should just be able to carry that throughout the spec.

from ev3dev-lang.

I'm open to changing this attribute to stop_action or something like that. Just open an issue in the main ev3dev issues if this is something you think we should do.

from ev3dev-lang.

I see now, I thought http://www.ev3dev.org/docs/tutorials/tacho-motors/ was the documentation, which is not quite as clear. I didn't realize there was a separate page of non-tutorial documentation...

from ev3dev-lang.