Has the bug occured in previous versions? If yes, please specify version(s): No. This we're certain of.
Description of the bug:
Found a bug with 3.02's interaction with the VSTi Motion by Ugo. In any context, pressing the shift key opens the MIDI Mapping dialog, with the VSTi selected in the plugin field. I also noticed that MIDI Learn is active in the dialog.
The MIDI Mapping dialog will open in such a case from every tab, and IN ANY MODULE FORMAT (even MOD, which doesn't allow MIDI Mapping), whenever the shift key is pressed.
During testing, the keymaps were changed (in case of a corrupted keymap file), but the behavior still existed. The behavior did not replicate with other VSTi's, nor with other VSTi's by Ugo. The input, both from the computer keyboard and MIDI keyboard, was disabled on several levels in case of a USB or keyboard error (the MIDI connection was disabled from Windows Audio settings, MIDI Record was turned off, the MIDI keyboard was turned off, Pattern Record was disabled, etc.), but the behavior was still present when pressing the shift key. Interestingly, the behavior is not immediate; you have to enter some notes in the pattern editor to "activate" the bug.
Furthermore, when Motion is loaded into the Chainer VST, the Shift key becomes unusable, as if the key is being hijacked.
The bug was definitely NOT present in .53 or earlier as we composed many tracks with this particular VSTi.
How often does it happen?: Usually always, but triggering the behavior is inconsistent.
How to reproduce (step by step description): Create any track and load Motion 2.8 by Ugo into the track. You may have to use it in a pattern or open the plugin GUI to start the trigger for the bug. Press Shift key in any context on any page. Normally this triggers the bug as described above.