Many of the methods in the display module are methods that are interfaces for the same methods in the display driver classes for device specific interpretation. I think there will be a better way to structure this so that there is a more explicit structure of what is expected by the driver modules. e.g. _update_status in the driver module should expect a specific set of variables, but this is implicit in the function call.
Seems wrong, needs thought on why it's wrong (or not) and how to improve (or not).
Many of the methods in the display module are methods that are interfaces for the same methods in the display driver classes for device specific interpretation. I think there will be a better way to structure this so that there is a more explicit structure of what is expected by the driver modules. e.g. _update_status in the driver module should expect a specific set of variables, but this is implicit in the function call.
Seems wrong, needs thought on why it's wrong (or not) and how to improve (or not).