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

chore(deps): Update @sindarius/gcodeviewer #1755

Merged
merged 1 commit into from
Jan 26, 2024

Conversation

TopoDiFogna
Copy link
Contributor

Description

Update @sindarius/gcodeviewer dependency to latest so it works also with gcode files generated by OrcaSlicer

Related Tickets & Documents

Closes #1752

Mobile & Desktop Screenshots/Recordings

No changes on frontend, just allows using the gcode viewer also with files from OrcaSlicer

[optional] Are there any post-deployment tasks we need to perform?

Update @sindarius/gcodeviewer to latest so it works also with gcode files generated by OrcaSlicer
@meteyou meteyou merged commit d34aa64 into mainsail-crew:develop Jan 26, 2024
8 checks passed
@meteyou
Copy link
Member

meteyou commented Jan 26, 2024

Thanks for your PR. I tested the G-Code again with Ocraslicer (my default slicer) and had no problems with the old version, but the update is still not wrong.

@TopoDiFogna
Copy link
Contributor Author

Very strange, I tried latest mainsail version with orcaslicer 1.9.0 and was not working. So maybe there some incompatibilities between latest orcaslicer and the "old" dependencies.

Anyway this fixes it with up to date software, like new users when installing everything from scratch.

@TopoDiFogna
Copy link
Contributor Author

Just for reference here's something sliced with orcaslicer that was not working with latest mainsail version
Carcassonne_tile_grid_MOD2_PLA_50m26s.zip

TopoDiFogna added a commit to TopoDiFogna/mainsail that referenced this pull request Feb 17, 2024
Update @sindarius/gcodeviewer to latest after fix in upstream library.

First update (d34aa64) was to include OrcaSlicer in the supported slicers list;
unfortunately it was including a bug where unlisted slicer features where aborting the rendering.

The new fix in the upstream library ensures that if supported slicers will add new features
the render will continue to work and unsupported features will have a generic color instead of
abort the render and throw an error.

See Sindarius/npm_gcodeviewer@be58cce
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot See GCode in VIewer when generating in OrcaSlicer
2 participants