Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate Image/Screen Classes #173

Open
eloiseyang opened this issue Jun 19, 2024 · 0 comments
Open

Integrate Image/Screen Classes #173

eloiseyang opened this issue Jun 19, 2024 · 0 comments

Comments

@eloiseyang
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant