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

Filament changes triggering Spool changes #329

Open
bofh69 opened this issue Mar 14, 2024 · 0 comments
Open

Filament changes triggering Spool changes #329

bofh69 opened this issue Mar 14, 2024 · 0 comments
Labels
Feature Request New feature or request

Comments

@bofh69
Copy link

bofh69 commented Mar 14, 2024

Is your feature request related to a problem? Please describe.

My client uses websockets to monitor spool changes. The payload contains the spool info, but also filament & manufacturer info.
My program uses those updates to update the slicer's filament configuration.

This works well, but I don't get updates to the spools when the filament or manufacturer info is updated. Therefore I also need to have a websocket for those, and I have to store the spools' data in memory so I can update the right spools when a filament or manufacturer is changed.

Describe the solution you'd like
It would be nice if it was possible to subscribe in such a way that I would get updates to all the spools using a filament/manufacturer when that is updated.

Describe alternatives you've considered
Just subscribing to all three data types, add an in memory model and update it there. It makes the program slightly more complicated though.

Additional context

@bofh69 bofh69 added the Feature Request New feature or request label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant