Add "servo" wrapper class to SoftPWMServo

[EmbeddedMan]

The idea here is that it will have exactly the same interface as the standard Arduino servo class, so you can just drop in SoftPWMServo.h instead of Servo.h and all existing sketches will just work.

[majenkotech]

You could inherit the Servo class as a parent then and override the relevant functions. That way the SoftPWMServo class can be passed to any functions that expect a Servo object. Means you have to include both Servo and SoftPWMServo (if you're not on UECIDE of course)...

[EmbeddedMan]

True. I've got everything done, for now, in a simple way. Next step is to
make it cleaner, as you suggest.

On Fri, Jun 26, 2015 at 6:47 AM, Matt Jenkins [email protected]
wrote:

You could inherit the Servo class as a parent then and override the
relevant functions. That way the SoftPWMServo class can be passed to any
functions that expect a Servo object. Means you have to include both Servo
and SoftPWMServo (if you're not on UECIDE of course)...

—
Reply to this email directly or view it on GitHub
#575 (comment)
.

[majenkotech]

Personally I'd like to see more interface classes defined in the core - things like the Servo interface, etc, that the libraries then use instead of defining their own interfaces. Makes for a much cleaner system.

[EmbeddedMan]

I completely agree. The trick, of course, is doing it without affecting
existing sketches.

On Fri, Jun 26, 2015 at 6:49 AM, Matt Jenkins [email protected]
wrote:

Personally I'd like to see more interface classes defined in the core -
things like the Servo interface, etc, than the libraries then use instead
of defining their own interfaces. Makes for a much cleaner system.

—
Reply to this email directly or view it on GitHub
#575 (comment)
.

[majenkotech]

Yeah, Arduino is a real millstone round our necks...

[ricklon]

Confirmed closed?

[EmbeddedMan]

This should be confirmed by somebody other than me before being closed. At least test it out that it works for them.