-
Notifications
You must be signed in to change notification settings - Fork 37
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
Gcodes subfolders not visible #136
Comments
CYD-Klipper should show the full path of every file. Creating a folder structure using Moonraker's api is quite difficult. So i haven't implemented it. Instead, a full path is shown. |
So also the files into subfolders are shown and can be printed?
Il giorno gio 2 gen 2025 alle ore 12:34 Sims ***@***.***> ha
scritto:
… CYD-Klipper should show the full path of every file.
Creating a folder structure using Moonraker's api is quite difficult. So i
haven't implemented it. Instead, a full path is shown.
—
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAV5ZAY6JIBYNY4BZRTAAYT2IUP3NAVCNFSM6AAAAABUPWYWPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRXGYZTQMRSGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Roberto Giuffrè
tel. +39-328-9140378
email: ***@***.***
pec: ***@***.***
|
Yes, they should be able to. Although, depends on the root of the path. https://moonraker.readthedocs.io/en/latest/web_api/#list-available-files Cyd-klipper only reads from the gcodes root. It will ignore the folder structure and list all files |
It's not able to navigate into gcodes subfolders.
I've configured a printer that when you insert an USB stick it uses udev to create a subfolder sda into printer_data/gcodes so it's possible to print from USB drive.
But CYD doesn't see and doesn't surf into subfolders of printer_data/gcodes.
But also if I want to create subolders for different materials like ABS, ASA, PLA, TPU, PETG, I can't see them to select the file to print.
The text was updated successfully, but these errors were encountered: