Replace On / Off split buttons for boolean settings with standard toggles or checkboxes #288

Open
opened 2026-04-05 16:19:34 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @derei on 3/17/2026

Is there an existing issue for this feature request?

  • I have searched the existing issues

The current On / Off split buttons make simple boolean settings harder to read than necessary.

For settings such as Timelapse, Auto Bed Leveling, etc., this pattern adds friction because:

  • it looks like a two-option selector, not a simple enabled/disabled state
  • it takes more effort to parse at a glance than a checkbox or switch
  • it slows visual interface scanning
  • it goes against the control style users already know from Windows, macOS, Linux, and Android

In a slicer UI, settings should be low-effort and immediately legible. These controls add interpretation cost without adding useful functionality.

Image

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

Replace the current split On / Off buttons with conventional boolean controls, such as:

  • intuitive toggles, or
  • checkboxes where a denser settings layout is preferred

This would improve:

  • state readability
  • scan speed
  • consistency with user expectations
  • overall usability of settings-heavy screens

For boolean settings, established UI conventions exist because they reduce cognitive load and make interfaces faster to use. In this case, a more distinctive/custom design makes the UI feel less intuitive, not more modern.
Segmented controls should be reserved for actual mode selection, not boolean states.

Current OS interfaces (windows, linux, macos), show the same unified style:

Image Image Image

Describe alternatives you've considered

No response

Additional context

This design choice goes against established UI/UX optimisations and makes the interface harder to use by adding small but repeated cognitive strains. That may not seem important when looking at one control in isolation, but in a world where almost everything around us is an interactive interface, those small frictions add up quickly. Forcing a less efficient visual interaction creates brief moments of hesitation and misreading, which can lead to the wrong option being selected.

*Originally created by @derei on 3/17/2026* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? The current On / Off split buttons make simple boolean settings harder to read than necessary. For settings such as Timelapse, Auto Bed Leveling, etc., this pattern adds friction because: - it looks like a two-option selector, not a simple enabled/disabled state - it takes more effort to parse at a glance than a checkbox or switch - it slows visual interface scanning - it goes against the control style users already know from Windows, macOS, Linux, and Android In a slicer UI, settings should be low-effort and immediately legible. These controls add interpretation cost without adding useful functionality. <img width="695" height="246" alt="Image" src="https://github.com/user-attachments/assets/bea52305-6c7b-4da2-8adf-9471f6753011" /> ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like **Replace the current split On / Off buttons with conventional boolean controls, such as:** - intuitive toggles, or - checkboxes where a denser settings layout is preferred This would improve: - state readability - scan speed - consistency with user expectations - overall usability of settings-heavy screens For boolean settings, established UI conventions exist because they reduce cognitive load and make interfaces faster to use. In this case, a more distinctive/custom design makes the UI feel less intuitive, not more modern. Segmented controls should be reserved for actual mode selection, not boolean states. Current OS interfaces (windows, linux, macos), show the same unified style: <img width="170" height="185" alt="Image" src="https://github.com/user-attachments/assets/0f8a9857-5509-44b2-a60c-30573e175b74" /> <img width="181" height="81" alt="Image" src="https://github.com/user-attachments/assets/f26e11a5-aae4-44cd-b469-f2fb408ba655" /> <img width="226" height="186" alt="Image" src="https://github.com/user-attachments/assets/39bc03aa-52dd-4c00-a03c-128e57ef7c4a" /> ### Describe alternatives you've considered _No response_ ### Additional context This design choice goes against established UI/UX optimisations and makes the interface harder to use by adding small but repeated cognitive strains. That may not seem important when looking at one control in isolation, but in a world where almost everything around us is an interactive interface, those small frictions add up quickly. Forcing a less efficient visual interaction creates brief moments of hesitation and misreading, which can lead to the wrong option being selected.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#288