Timeline for Designing interfaces to hardware
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2015 at 15:39 | vote | accept | rwstoneback | ||
| Jan 11, 2015 at 15:38 | comment | added | rwstoneback |
Thanks for the response! Most of my devices have 90% of the same features. But then I have devices that have a handful of unique features, like the Vibration and BacklightColor that you mention. I'd like to keep the functions explicit to avoid the user having to rely completely on documentation. So instead of the BooleanFeature that you mention, I could maybe have each Feature be a struct. So Vibration would be a struct which is passed to Widget::setFeature() or returned from Widget::getFeature(). I think that would work, however I might end up with a lot of structs.
|
|
| Jan 10, 2015 at 20:50 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |