Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Under Linux, re-opening the Plotter within a peristent context may not deallocate resources. Allow this via an explicit .close() method.
Hardware tests added:
Addendum: I am looking into some class restructuring such that the silhouette can be used by other front ends plus facilitation of derival such that no functionality is broken or compatibility is disrupted. Roughly, this would:
Graphtec
class into a hierarchy, avoiding product code comparison within member functionsGraphtec
into a function call that returns the properly detected classOpinions?
For verification, more umockdev ioctl traces would be required and a reference test to be added. I currently have access to a cameo3 only. Appreciating any 'foreign' ioctl files for further I/O verification to start with (test_io.py).