Description
This feature request proposes the ability to convert an existing widget between Fader and Dial types without having to delete and recreate the widget. The goal is to streamline the UI customization workflow and preserve widget configurations during visual adjustments.
Problems
  • Redundant Workflow
    : Currently, if a user wants to switch a Fader widget to a Dial (or vice versa), they must manually delete the original and recreate the new widget from scratch.
  • Loss of Configuration
    : This process risks losing existing bindings, parameter settings, styles, and actions tied to the original widget.
  • Time-Consuming in Complex Layouts
    : In large or layered setups, replacing one widget type with another can disrupt the design and require manual re-alignment and reconfiguration.
Proposed Solution
  • Widget Type Switch Option
    : Add a toggle or dropdown in the widget settings to convert between Fader and Dial types.
  • Preserve All Attributes
    :
- Parameter bindings
- MIDI/OSC mappings
- Actions and behaviors
- Size, styling, and position
  • Optional Appearance Reset
    : Offer a checkbox to reset to default style for the new type, or retain the current styling where compatible.
Examples
  1. Layout Tweaking
    : A performer wants to switch a vertical Fader to a compact Dial for better space usage, without redoing parameter assignments.
  2. Aesthetic Adjustments
    : A user redesigns a page layout and prefers Dials for consistency. With this feature, they can quickly convert all Faders without data loss.
  3. Iterative UI Design
    : During testing, a creator toggles between widget types to decide which feels best, without re-binding or repositioning every time.
Benefits
  • Faster UI Prototyping
    : Enables fluid workflow for experimenting with control layouts.
  • Preserved Logic
    : Maintains all functional connections and behaviors.
  • Better UX
    : Saves time, reduces error risk, and improves overall design flexibility in Loopy Pro’s UI system.
This summary was automatically generated by ChatGPT-4 on 2025-05-16.