You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The filter display does not match the filter type shown in the 'general' card:
Switch the filter type using the dropdown: the filter display stays the same. Expected: it updates to the correct type.
The display updates when a click happens in a non-widget part of the 'general' card. For example at the location of the cross in the above screenshot. The view then becomes correct, and switching the filter type correctly works. This is the correct view:
The same behavior happens with the "sub" and pad > envelopes tabs.
The text was updated successfully, but these errors were encountered:
After tinkering with the UI a bit more I realized that it's working as intended. What I missed is that what the graphical display shows depends on which panel (general / envelope / lfo) is active. Unfortunately there is no visual indication of that.
One option would be to have the panel's header highlighted, the same way "filter" or "global" are shown.
Having a visual hint there would be good IMO, though likely it should be more subtle than the filter/global highlighting to avoid distracting the user with an element in the center of the screen.
That's a possible solution, though adding the a slight highlight to the titlebars would create an added bonus of hinting that they're clickable which I've heard in the past is a UX issue with the current implementation.
Step to reproduce the issue:
Launch
The filter display does not match the filter type shown in the 'general' card:
The display updates when a click happens in a non-widget part of the 'general' card. For example at the location of the cross in the above screenshot. The view then becomes correct, and switching the filter type correctly works. This is the correct view:
The same behavior happens with the "sub" and pad > envelopes tabs.
The text was updated successfully, but these errors were encountered: