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

filePath and in-memory use instead of local FS #19

Open
zstima opened this issue Dec 4, 2020 · 2 comments
Open

filePath and in-memory use instead of local FS #19

zstima opened this issue Dec 4, 2020 · 2 comments

Comments

@zstima
Copy link

zstima commented Dec 4, 2020

could u push something else in filePath parameter of the DarwinWidget
so it doesnt save it in a file but instead gives u a object in the memory which contains the image ?

@cagbal
Copy link

cagbal commented Jan 5, 2021

This would be really nice.

@ishaan1995
Copy link
Contributor

ishaan1995 commented Feb 18, 2021

Hey @zstima
Using in-memory image object can be tricky given images can have a large size.
Usually it's easy to push the captured image on disk which can be later retrieved and reduced in size for preview.

Regarding the filePath parameter, it can be a local file path or something outside the app scope as well. (Report a bug here in case it's not happening).

Nonetheless, If you find better implementations of handling images in-memory, do share & feel free to raise a PR.

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

3 participants