We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Chrome
Desktop PC
Windows
I struggle at calling this a bug, but it is definitely noteworthy and likely warrants rectification in some/many minds.
On:
I observe:
Can the ordering adopt a numerical sequencing approach (in my case, start at T0 on left and end at T11 on far right)?
Thanks.
~MHz
See tools ordered in a logically ascending sequence from T0 on left to Tn on far right.
Presumably have a config that includes macros for tools T0 to T11.?.
Please change this issue to a feature request if this doesn't merit being classified as a bug. :)
Or I can do so if warranted/desirable, or I can close this and open a FR issue - just let me know. TIA.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Browser:
Chrome
Device:
Desktop PC
Operating System:
Windows
What happened?
I struggle at calling this a bug, but it is definitely noteworthy and likely warrants rectification in some/many minds.
On:
I observe:
Can the ordering adopt a numerical sequencing approach (in my case, start at T0 on left and end at T11 on far right)?
Thanks.
~MHz
What did you expect to happen instead?
See tools ordered in a logically ascending sequence from T0 on left to Tn on far right.
How to reproduce this bug?
Presumably have a config that includes macros for tools T0 to T11.?.
Additional information:
Please change this issue to a feature request if this doesn't merit being classified as a bug. :)
Or I can do so if warranted/desirable, or I can close this and open a FR issue - just let me know. TIA.
~MHz
The text was updated successfully, but these errors were encountered: