Is your feature request related to a problem? Please describe.
There is no integration between the Screen class and the Image class. The Screen.image property returns a numpy array, when we could return an Image class. Image and Screen share some values too that could be passed along easily.
Describe the solution you'd like
The Screen.image class should output Image classes. Image should be a frozen single shot version of Screen, and the parent Screen should be recoverable from the Image class alone. The passed Image class should contain all the relevant metadata from its parent Screen.
Describe alternatives you've considered
We could combine Image and Screen into an all in one tool to reduce the total number of objects necessary for image processing tasks. This solution would muddle the distinction between machine interface and data container, and increase syntactic complexity over time.
Is your feature request related to a problem? Please describe. There is no integration between the
Screenclass and theImageclass. TheScreen.imageproperty returns a numpy array, when we could return an Image class.ImageandScreenshare some values too that could be passed along easily.Describe the solution you'd like The
Screen.imageclass should outputImageclasses.Imageshould be a frozen single shot version ofScreen, and the parentScreenshould be recoverable from theImageclass alone. The passedImageclass should contain all the relevant metadata from its parentScreen.Describe alternatives you've considered We could combine
ImageandScreeninto an all in one tool to reduce the total number of objects necessary for image processing tasks. This solution would muddle the distinction between machine interface and data container, and increase syntactic complexity over time.