Show hidden settings in dev mode #1441

New Issue

MrUnknownDE · 2026-04-05T17:46:55+02:00

MrUnknownDE commented

2026-04-05 17:46:55 +02:00

Originally created by @Azio-Pantheon on 12/2/2025

Description

I have seen this conversation comes a lot in discord, so I took a quick look at how we can improve this. The 3 proposed solutions are:

Ability to toggle visibility of individual settings like Cura. This requires a rewrite of the whole config system plus additional UI for managing the settings. I dont think any of the devs here cares about this issue enough to do this.
Make hidden options in search result more clear. Currently, when the user searches and finds a hidden setting, and then clicks on it, orca brings the panel up but it doesnt show the setting. I would love that if the user clicks on a hidden setting in search result, it tells the user why this setting is hidden, but this also requires quite a bit of work to go through every single setting, manage the search messages plus UI work. I think there might be an easier to implement solution: when a user searches and clicks on a setting from the search result, it forces the setting to show up(if it were hidden, then show it as disabled).
Show all options, if an option is depended on another that is currently off, show as disabled. This is the easiest solution to implement, but it makes the UI super crowded.

I am going with solution 3 for now. and maybe try solution 2 if I get back to this. But I want to create this PR so that if people really want to see all settings, they can grab it in the artifact here.

Bug: togggling dev mode doesnt auto refresh the settings panel. You have to switch to another tab to update the UI.

This is my attempt to address #11001

Screenshots/Recordings/Graphs

Tests

*Originally created by @Azio-Pantheon on 12/2/2025* # Description I have seen this conversation comes a lot in discord, so I took a quick look at how we can improve this. The 3 proposed solutions are: 1. **Ability to toggle visibility of individual settings like Cura**. This requires a rewrite of the whole config system plus additional UI for managing the settings. I dont think any of the devs here cares about this issue enough to do this. 2. **Make hidden options in search result more clear**. Currently, when the user searches and finds a hidden setting, and then clicks on it, orca brings the panel up but it doesnt show the setting. I would love that if the user clicks on a hidden setting in search result, it tells the user why this setting is hidden, but this also requires quite a bit of work to go through every single setting, manage the search messages plus UI work. I think there might be an easier to implement solution: when a user searches and clicks on a setting from the search result, it forces the setting to show up(if it were hidden, then show it as disabled). 3. **Show all options, if an option is depended on another that is currently off, show as disabled**. This is the easiest solution to implement, but it makes the UI super crowded. I am going with solution 3 for now. and maybe try solution 2 if I get back to this. But I want to create this PR so that if people really want to see all settings, they can grab it in the artifact here. Bug: togggling dev mode doesnt auto refresh the settings panel. You have to switch to another tab to update the UI. This is my attempt to address #11001 # Screenshots/Recordings/Graphs <img width="392" height="599" alt="image" src="https://github.com/user-attachments/assets/babc5933-4c02-4996-895e-70102a4a1f5f" /> ## Tests

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#1441