AJ Kerezy
Original Post:
Description:
Allow users to define
default settings per widget type
(Button, Fader, Dial, Text, Radio, Meter, etc.) so newly created widgets inherit preferred
visual styles
and
behaviors
(actions, guards, ramps, visibility rules, label templates)—with defaults scoped to
Global
,
Project
, and
Page
.
Problem:
Every new widget starts from factory settings, forcing repetitive styling and reconfiguration (colors, fonts, outlines, ramp curves, quantize/late-press guards, default actions). This is slow, error-prone, and leads to inconsistent UIs across pages and projects.
Proposed Solution:
  • Scopes & Priority:
    Defaults at
    Global → Project → Page
    ; the most specific scope wins. Per-type entries (e.g.,
    Button
    ,
    Fader
    ) plus optional
    subtype profiles
    (e.g.,
    Button: Transport
    ,
    Text: Small Label
    ).
  • What a Default Can Include (checklist):
-
Visual:
size anchors, colors/tints, fonts, borders/rounding, icon/pictogram/Genmoji, safe text size, background image mode.
-
Behavior:
prewired
actions/follow actions
, quantize and
late-press guard
,
ramp
defaults, toggle policies, visibility rules.
-
Mappings (optional):
include/exclude
MIDI/Keyboard/OSC
learns; auto-scope retargeting (e.g., map to
selected clip
).
-
Label Templates:
tokenized text (e.g.,
Play {clip.selected.name}
) and number formatting.
  • Capture & Apply:
-
“Save as Default for This Type (scope…)”
from any configured widget.
- New widgets adopt the active default automatically;
Override
per instance remains possible.
-
Reset to Factory
or
Reapply Current Default
commands.
  • Management UI:
-
Defaults Manager
with thumbnails, tags, and diff view; enable/disable fields included in a default.
- Export/import
Default Sets
(team sharing) with asset de-duplication.
  • Compatibility with Presets:
- Defaults =
auto-applied baseline
;
Presets
remain for named variants you apply manually or link to. Option: “After create,
apply preset X
.”
  • Actions & Variables:
- Actions:
Save Current Widget as Default (scope/type)
,
Set Active Default (scope/type)
,
Reset to Factory
,
Reapply Default to Selection
.
- Vars:
defaults.scope.active
,
widget.default.applied
,
widget.default.sourceScope
(Global/Project/Page).
Benefits:
  • Dramatically faster page building; fewer repetitive steps.
  • Consistent look & behavior across large projects and teams.
  • Fewer mistakes (guards/quantize/ramp policies are standardized).
  • Clean separation between
    auto defaults
    and
    optional presets
    .
Examples:
  • Set a
    Button
    default with bar-quantized actions and a 120 ms late-press guard; every new Button comes pre-armed.
  • A
    Text
    default uses a high-contrast font with
    {tempo.bpm|0}
    formatting for status labels across pages.
  • On a FOH page, define
    Fader
    defaults as compact with numeric trims; on the main page keep full-height faders—via
    Page-level
    defaults.
  • Share a
    Global Default Set
    with your band so new widgets match branding and behavior out of the box.
This summary was automatically generated by GPT-5.1 Thinking on 2025-11-24.
Default Widget Settings
Allow users to create /set defaults for widgets, and then whenever widgets are used in any of their projects, their desired are already "set" or "defaulted.
E.g. - in all of my use of STEPDIALS, I want the State Feedback setting disabled, by default. So allowing users to create default settings, they won't have to SPEND HOURS, remembering what /how they set up something. Having to look in other projects is terribly TIME consuming.
~Thanks for great software~
AJ