-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature Request: show models inside zip archives #29
Comments
Hi there, Looking at a possible implementation:
Thank you for your feedback |
Hey!
Not really but that could also be a valid reason. Of the two proposed methods I like more the second options, to extract them to a temp folder and clear them after a while (I especially like the option to automatically deleted them after some time). Thanks! |
This feature would be easier to implement if I would implement this one first |
This is similar to my biggest pain point with TagSpaces right now: I cannot view .7z contents. Personally the way I see it being done is the same way 7-Zip already does it (and can be run w/ that in the backend) is that it opens a temp folder and uses that in the GUI. |
@gentleAmateur this issue is being discussed here #30 |
This feature is now fully implemented in the V2 branch, further discussion will be held here Maker-Management-Platform/agent#136 |
Hi there!
First of all, really cool project!
I've started playing with the project a couple of days ago, and I believe the main missing thing (at least from my side) is the ability to see the models inside a zip archive (or any other compressed file for what it matters).
Further details:
In the years I've grown quite a collections of STL (300+ GB) which where stored using Nextcloud (similar to what was briefly described in the last comment here #11 ). Many of these files are inside an archive (from source, repacked be me, etc.) and seems there is no way to show what's inside.
I could upload pictures of the main file / printed object but it's not really the same (in my opinion at least)
Here the current behaviour I'm getting.
Beside this "nice to have", really cool project!
Thanks!
The text was updated successfully, but these errors were encountered: