I’m so glad to have found this thread. I never knew about the double-click or shift-click approach to opening plugins instantly (without the lag). I’ve been troubleshooting my system for so long to get rid of this annoying delay, rolling back graphics card drivers, changing power settings–everything under the sun. I never would have imagined this was designed on purpose. Weird!
This is extremely counter-intuitive compared to how most programs function. I’ve never had a program intentionally trigger a delay before completing the action and I really can’t wrap my head around the explained purpose. As a simple solution: Why not let the single click–the action most of us will use when working quickly–trigger the fast plugin open, and the shift-click be the laggy one (to fulfill whatever arcane purpose that may be)?
This is no doubt kicking you support requests you don’t need and causing frustration to everyone else out there like me who wouldn’t imagine a developer would program intentional lag into buttons.