HugoPeters/DreamStream

Consider design change for emulated vs incoming devices

HugoPeters opened this issue · 0 comments

As all setter functions will behave differently on an emulated device, is there a real point in keeping them in them as-is in the base class?
Let's look at a better way of dealing with this (perhaps multi-inheritance?) so that the logic can be sort of separated without ugly overrides everywhere.
Also, gotta think of a better naming convention for emulated and incoming devices.