Dropdown Menu Widget for Preset/Value Selection
under review
m
mccy
Description:
Add a new dropdown menu widget for selecting values or presets. This would offer an alternative to the current dial/stepper selector, providing better usability, especially with longer lists or precise selections.
Problem:
The dial widget is too fiddly for precise selection, especially with long lists (e.g., presets for AUv3 plugins). Users can’t see full label names, must scroll back and forth, and often select the wrong value. The lack of overview limits live usability and efficiency.
Proposed Solution:
– Introduce a new dropdown menu or matrix selector (e.g., 8×8 or 16×16 grid)
– Allow full menu and individual entry customization (e.g., label line breaks, truncation options)
– Auto-size width to longest label or allow manual width settings
– Let users define how many entries above/below the cursor are shown while scrolling
– Option to scroll with one control (dial/MIDI) and trigger with another (button)
– Highlight active item visually (bold font, color, size)
Benefits:
✅ Much better visibility of menu entries
✅ Faster and more reliable preset selection
✅ Frees up space on canvas by replacing multiple stepper widgets
✅ Ideal for live performance and AUv3 plugin integration
✅ More scalable UX for large value lists
This summary was automatically generated by ChatGPT-4 on May 2, 2025.
AJ Kerezy
I feel like this is one of MANY feature requests that are related to issue that you can't select something - without the actions (or triggers) from the steps along way executing when you don't want them to. This is needed is for TRUE preset selection. A year later..... LP still doesn't fully support presets
https://www.youtube.com/watch?v=8zlWuaDs_9g
j
joggler
Agree with Mccy. Too fizzy to dial in a precise value.
atafator
I would also appreciate a dropdown menu. Unfortunately, the stepper dial does not allow to read the previous and subsequent entries of the currently selected item, which means that you can only read them by scrolling back and forth, which is necessary but annoying extra steps.
ultracello
Ideally you can
- per dropdown menu (means the full menu)
and
- per dropdown menu entry
define how menu entries will behave if the label text is longer than the menu width:
- use auto line break OR use [...].
- use max. x line breaks
ultracello
An alternative (which I personally find much worse, because it is less configurable and individual) would be:
Maybe you could specify that the width should automatically be as long as the longest preset name or label of a menu item. And/or even better: for manual widths set by the user - in case the preset name turns out to be longer after all - linebreaks are set automatically, so that no preset name disappears behind an unsexy looking [...].
D
Daniele Peters
I like dropdown menus much better too.
ultracello
Merged in a post:
Widget: drop-down menu
l
lemon tree
A
Anders Trick
A dropdown menu widget, hooray! What a great idea!
ultracello
Ideally, when scrolling, you can individually set the number of entries BEFORE and AFTER the currently selected entry. In order not to remain in the dark when scrolling. For example: above and below the cursor always 1, 2, or 5 or whatever further entries are displayed. That would be hard sexy.
ultracello
Ideally we can have a broad scrollbar on the right side to avoid accidents when choosing the correct preset/entry.
Or way better: give us the ability to scroll up and down entries but trigger an entry with another action button / MIDI control. That would be damn smooth!
ultracello
Merged in a post:
dropdown menu widget
T
ThinKool
Load More
→