Manchester update: Still no working "route all keyboard strokes to plugin".

A serious bug from the earlier days of SONAR is still inherited in the latest Manchester release. It still keeps preventing me from using SONAR for really serious projects with a lot of VST's and more sound modules. The reason for that is that some VST's are requiring that ALL of the computer keyboard strokes are routed to the plugin and not to SONAR as the DAW. Especially when VST's are shown in the foreground this should be no problem at all. SONAR has a special button that should be routing all keyboard strokes when lit, but this does not work. Shortcuts of SONAR itself keep on working whether the button is lit or not.
Why is it that Cubase does not have such button with their VST's and all of the VST's that can use the computer keyboard can use the computer keyboard. So it must be simple! I hope that the programmers of Cakewalk will take the time to fix the ancient problem.
 
Question on this forum: Anyone who knows a good workaround (mine is now using Cubase for serious editting of VST's that require it)?

The trouble I have is with is with the EMU Emulator 3. I know it is an old one and as a matter of fact the manufacturer EMU does not exist anymore. But for me it still one of the best plugins I have, I use it often.
So for me, like you had with U-he, no upgrade or update of the plugin itself.
 
I still think that Cakewalk has to program something. They claim that hitting the "keyboard" icon does redirect all keyboard input to a plugin. Somehow I do think that they have forgotten something here, because why is it that keyboard input still are addressed to SONAR while having the keyboard icon lit? I have no explanation. Also with other DAWs like Cubase for example the keyboard input is redirect to the active window (the plugin). This is normal windows behaviour, so why on earth should SONAR want do it differently?
 
I hope one time there the clue will be found to this simple question. Anyway at least you also had the problem and that shows that there is a flaw within SONAR that causes this.
 
Geert