SoftFever
QoL: Make hidden options in search result more clear
Choose any option that could be hidden under certain conditions, for example the "Overhang speed: Classic mode" toggle is only displayed if "Slow down for overhangs" is turned on:
Then turn "Slow down for overhangs" off, which should hide the "Classic mode" option.
Then search "Classic mode", which shows this option:
But if you click it, the app switches to the "Speed" panel but doesn't show the target option, which is confusing.
We should somehow tell the user that this option is currently hidden/disabled/unapplicable in search result, for example by adding a "(Disabled)" prefix/suffix to the result, or grey out the result, etc.
I don't want to hide the option from the result, because when you are using search, it's better to tell you that we have that option but it's not usable at the moment and you might need to do some other things first to enable it, other than just hide it which doesn't give user any meaningful information.
Yeah, I bumped into this as well and thought I was going nuts not seeing an option (didn't realize it was hidden by another).
Maybe a solution would be to not hide the option, but gray it out as disabled (bonus points for updating the mouseover tooltip to say what disabled it)? That's a more common way of handling UI elements, since shifting / hiding things can confuse users ("gray not takeaway"). Plus, it handles the search situation since it's no longer hidden the user gets a clearer view when they go to it and see it's been disabled.
I vote for it being greyed out and not hidden. I find that hidden settings are less user friendly in general and you end up in a where's Waldo situation? That would also users to still be able to search for the feature so they know its there.
Another Idea I had is that if you try to enable/click on a disabled setting it would tell you what setting would need to be enabled to allow it to be used. Esentually provide information to the user of the feature that supersedes it.
I don’t know how many Prusa based settings are not visible in Orca at all, but I have a hunch that it’s too many to make graying them out applicable. Some of them aren’t in use in Orca under any situation.
I think a good one might be if Disabled (?) was displayed in the search results with either a mouse hover tooltip or a popup after a click saying that the visibility depends on other settings, or if it is replaced by other settings altogether. And clicking the result wouldn’t do anything else, not even close the search results. That way the user can easily revise the search.
The hard part about this is that the option is not coded in a way that it knows it is dependent on another option, rather there is a method run whenever the config is updated and in there, you manually check if an item is toggled, then hide/reveal manually. To implement this, it would probably be a rehaul of this system by having a callback function on the options themselves.
GitHub bot: this issue is stale because it has been open for 90 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Orca bot: this issue is stale because it has been open for 90 days with no activity.
Orca bot: this issue is stale because it has been open for 90 days with no activity.
Orca bot: this issue is stale because it has been open for 90 days with no activity.
Orca bot: this issue is stale because it has been open for 90 days with no activity.
Needs bumping, as hiding options, rather than disabling them, confuses users who may never know that option is even possible depending on what config they start with.
Orca bot: this issue is stale because it has been open for 90 days with no activity.
Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.
This issue came up again today on Discord. It really needs to be re-opened and implemented. When Advanced or Developer mode is active, ALL settings should remain visible to the user and only "grayed out" when disabled, never hidden.
Link to the issue today: https://discord.com/channels/1137181739773603922/1137184602289610782/1425590844261531670
