Click on a button, then pressing the Return key toggles the state, or steps through the button states (steps through filter-slopes, mod-dests, arp-range). Very convenient for the Mod Dest selection – instead of clicking N times, just hit return a few times. Cool! 
Nice find; I didn’t even know about this
thanks!
Hi,
It is not working on my system.
Would be great!
Tell me more!
Regards Luloop
Hi, LuLoop!
Tell you more? 
There’s not much more to say! Click on a button, then hitting the Return key will toggle the button on/off. Or, if it is a button that selects between different settings, pressing the Return key will step through the settings. For me this works for both 0.9.28 and 0.9.33 (the two versions that I have installed).
Here’s a bug though (hey, Gil 
):
- click on the Filter Slope button
- hit return, it toggles through the settings
- move the pointer to hover over the Filter’s EG Amount knob
- the pop-up appears and shows you the number for the EG Amount
- press return, and the same pop-up connected to the EG Amt now shows the text description of the filter slopes: 6db/Oct … 24 db/Oct (but shouldn’t they be -6 … -24?)
db-oct.tiff (40.5 KB)
This particular behavior happens only for value-picker buttons; a plain on/off button won’t affect the pop-up display for a knob, although the return key still toggles the button on and off while the knob value is shown. And it “works” for any value-picker button and any knob. Change the Glide Type, then hover over an envelope knob, hit return and see the popup attached to the envelope knob cycle through the glide type strings while the simulated LEDs for the glide type cycle through their pattern.
Of course, there’s the added complication of the lower edit panel, and how interactions don’t cross that boundary. I just discovered that, and can’t explain it well enough right now. It seems like the upper and lower panels “remember” their own last-clicked-on button, and that’s the one that gets invoked when the return key is pressed.
Another small bug (hey, Gil ) Just a little typo: the display names for the Glide Osc 1 + 2 is different from the Osc 1+2 buttons for Mod1 and Mod2. The Glide has OSC and BOTH, while the two Mods have Osc and Both. Just a trivial inconsistency.
So, it’s a little schizophrenic… buttons don’t display values, but apparently they really want to, and so they take over any existing popup, and use it to show their values. Naughty, naughty buttons. 
I don’t know why the return key wouldn’t work for you, and I don’t know why my system should be “special”, although with the double-click knob issue, I guess it is, somehow. Maybe it’s some trackpad setting? I’ll go look into it…
Hi,
A nice easter egg.
Smooth Regards Luloop
Thanks for the detailed report Mike.
I will document this, but please note GUI items are lowest priority at this point, as we’re heading the release. We are concentrating at major level functionality related issues at the moment.
Another small bug (hey, Gil ) Just a little typo: the display names for the Glide Osc 1 + 2 is different from the Osc 1+2 buttons for Mod1 and Mod2. The Glide has OSC and BOTH, while the two Mods have Osc and Both. Just a trivial inconsistency.
I wasn’t able to find it, can you attach a screenshot please ?
Hi Gil,
- click on the button “Osc” (dest.) in the GLIDE section once
- press “enter” - the destination will change with every pressing
- hover the mouse cursor over a another pot to show the value
- press “enter” again, the value changes to display the osc destination (“BOTH”, “OSC1”, “OSC2”)
do the same with osc destination under the pitch amt knob:
- click on the button “Osc” (dest.) in the Mod1 section once
- press “enter” - the destination will change with every pressing
- hover the mouse cursor over a another pot to show the value
- press “enter” again, the value changes to display the osc destination (“Both”, “Osc1”, “Osc2”) - lower case instead of upper case.
greets, bernard
btw, I like that feature
Hi,
Easter egg is gone… with the 1.1.16/0.9.36
Regards Luloop