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

Read and Write, Needle for Color_Change. #45

Open
tatarize opened this issue Jul 15, 2018 · 0 comments
Open

Read and Write, Needle for Color_Change. #45

tatarize opened this issue Jul 15, 2018 · 0 comments

Comments

@tatarize
Copy link
Contributor

One of the few breaking changes that might be doable. Reading color change commands could and maybe should be flagged with the needle provided. Some formats like .u01 overtly give this information and might be needed to express where sequins should be in particular layers where that information is not overtly given within the format but where the sequins are linked to a particular needle. Such information would be unrecoverable without storing the needle number present in the format command statement. Writing this information wouldn't require any breaks it would just use null-op for color and default to the current behavior, but loading would be flagged with additional information and rather than command == COLOR_CHANGE, command == (COLOR_CHANGE & COMMAND_MASK), could break some elements that failed to account for that.

This could also be triggered optionally, by loading with some settings flag that basically means give the needle number used. Also it is typical in many formats that STOP is actually encoded by selected the same needle back to back.

lexelby pushed a commit that referenced this issue Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant