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

Documentation: adapt to change in label objects option in PrusaSlicer #1665

Closed
tweh opened this issue Nov 25, 2023 · 4 comments
Closed

Documentation: adapt to change in label objects option in PrusaSlicer #1665

tweh opened this issue Nov 25, 2023 · 4 comments
Labels
⚡ Type: Bug Something isn't working

Comments

@tweh
Copy link

tweh commented Nov 25, 2023

Mainsail Version:

2.8.0

Browser:

Safari

Device:

Laptop

Operating System:

macOS

What happened?

I’m not sure whether this is the right place to report this since this is a thing that should be change in the documentation and not a real bug. With version 2.7.0 Prusa Slicer changed it’s option Label Objects to become a drop down and thus the screenshot in the mainsail docs . So at the moment the docs show only a check box, where as far as I understand one must 1. select Firmware-specific and 2. in the Print settings and Klipper as g-Code flavor in the printer settings.

What did you expect to happen instead?

The docs should look like this:


In PrusaSlicer or SuperSlicer you have to chose Firmware-specific in:

Print Settings > Output options > Output file > Label objects

Bildschirmfoto 2023-11-25 um 15 57 41

And you maust ensure that in the printer settings you choose Klipper as G-code flavor. You’ll find this in:

Printer Settings > General > Firmware > G-code flavor

Bildschirmfoto 2023-11-25 um 15 57 49

How to reproduce this bug?

read the docs ;-)

Additional information:

No response

@tweh tweh added the ⚡ Type: Bug Something isn't working label Nov 25, 2023
@tweh
Copy link
Author

tweh commented Nov 25, 2023

Found the doc report and re-postet the issue there.

@tweh tweh closed this as completed Nov 25, 2023
@meteyou
Copy link
Member

meteyou commented Nov 25, 2023

@tweh sry... i don't find your re-post...

@tweh
Copy link
Author

tweh commented Nov 26, 2023

I’m sorry! Could have linked it …

Her it is: mainsail-crew/docs#41

@meteyou
Copy link
Member

meteyou commented Nov 26, 2023

ohh ok. this is the old repo. the new docs are in https://github.com/mainsail-crew/gb-docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚡ Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants