AuburnSounds / AuburnSounds/Dplug

"Disabled" widgets

Open
#644 1 comment 0 reactions 0 assignees View on GitHub
Enhancement Question
Dominant language
D
Stars
564
Forks
34
PR merge metrics
No merged PRs in 30d

Description

A useful class for widgets are conditional, and "enabled" only when certain Parameter conditions are met.
Typically, interacting with them will force one of these conditions too.
Right now, the widget is forced to listen to these "enabling" parameters.

Is there something more composable? So that the same widget could work with a Parameter that can be disabled by another Parameter, or just vanilla and never be disabled.

Should the disabled state be in Parameter?
Should the disabled flag be in UIElement?

Contributor guide

Open the contributing guide

Research direction

Start by tracing how widgets currently listen to enabling Parameters, then compare the roles of Parameter and UIElement in the existing widget code. Decide where a composable disabled state belongs and define how the same widget should work with a conditionally disabled Parameter or with no disabling behavior; the issue provides no file or test names.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.