You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could first order in alphabetical order by machine and group by machine type or just by the order specified in config.yml while non "registered" devices drop to either top of bottom of the list of devices (could easily group them by the detected machine type). Though there is also an ask to pair a ferm with a iSpindel (some use these together) so a concept of "linking" devices could also work well here as well.
Ideally adding a way to "register" a device that has been detected by the server would also go to improve this.
Another take on this feature would be to add a sortOrder: <number> into the config.yml structure to then provide a complete ordering of all machines and allow mixing of machines together (Pico, still, ferm, iSpindel, Z, still , ferm, etc).
The text was updated successfully, but these errors were encountered:
To help keep things consistent and expected.
This could first order in alphabetical order by machine and group by machine type or just by the order specified in config.yml while non "registered" devices drop to either top of bottom of the list of devices (could easily group them by the detected machine type). Though there is also an ask to pair a ferm with a iSpindel (some use these together) so a concept of "linking" devices could also work well here as well.
Ideally adding a way to "register" a device that has been detected by the server would also go to improve this.
Another take on this feature would be to add a
sortOrder: <number>
into the config.yml structure to then provide a complete ordering of all machines and allow mixing of machines together (Pico, still, ferm, iSpindel, Z, still , ferm, etc).The text was updated successfully, but these errors were encountered: