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

Bedmesh: deleted meshes are not visible indicated in the UI #548

Closed
zellneralex opened this issue Jan 19, 2022 · 4 comments
Closed

Bedmesh: deleted meshes are not visible indicated in the UI #548

zellneralex opened this issue Jan 19, 2022 · 4 comments

Comments

@zellneralex
Copy link
Member

zellneralex commented Jan 19, 2022

Describe the bug:
If you delete a mesh in the UI there is no visible indication that it will be removed after the next save config and also that it is not usable anymore in the current klipper season

Expected behavior:
Any kind of visualization e.g cross out the name or a small trash can symbol next to the name.

Screenshots:
As you can see only the SAVE_CONFIG shows that somethings changed but you do not see which mesh I deleted
image

Logfiles:
Please upload your Logfiles here or upload them to pastebin.com and paste your log links here.
not needed

@zellneralex zellneralex added Prio: 3 Low ⚡ Type: Bug Something isn't working labels Jan 19, 2022
@Misterke
Copy link

This is a consequence of MainSail showing the meshes from the config as currently bed_mesh.py is not offering a way to report the actual available profiles. Feel free to get more attention for Klipper3d/klipper#5222 as that would allow solving this problem.

@meteyou
Copy link
Member

meteyou commented Feb 15, 2022

@Misterke thx for the info and the PR in klipper! with this PR, it would be very easy to fix this issue!

@Misterke
Copy link

@Misterke thx for the info and the PR in klipper! with this PR, it would be very easy to fix this issue!

The PR has been merged, so Mainsail could now use the actual profiles instead of the static config.

@meteyou
Copy link
Member

meteyou commented Feb 18, 2022

fixed with #660

@meteyou meteyou closed this as completed Feb 18, 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

4 participants