Unfortunately there seem to be a couple of bugs in the new KK 3.2.0 release instead of expected improvements.
At first, the internal link between the KK3.2.0 browser window and the related plugin window toggle mechanism seems to be totally broken now. Whenever a specific NKS library preset has been selected via an NI S-series MK2 keyboard while using the previous KK3.1.2 version, the NKS library view on the PC still changed to the related plugin view automatically (as long as the pin icon was not checked in the KK menu bar). Now, in the new KK3.2.0 version, regardless of that pin icon status, the plugin view will never show up automatically when selecting any preset via an MK2 keyboard. Why is that well-established functionality now broken at all? Why is the screen not following what a user is actually doing on the NI keyboard? It really seems that NI wants to make MK2 user's lives harder, or new product versions are not tested properly before releasing those. Instead of improving the KK3 app step by step (and to gain back great potential that has been lost in the meantime), KK is even losing more and more essential functionality that was already working before reliably. What a regression!
However, after switching over to the plugin window manually (at the KK application itself), in the new KK3.2.0 version the plugin view seems to be buggy as well. Some plugins, especially when based on UVI/Falcon 3.0 libraries, are not completely visible and appear to be messed up in KK3.2.0. Instead of showing the actual plugin information right under the KK plugin top menu, a big useless space/gap is now appearing. The plugin itself is shifted down to the lower half of the screen and is finally cut off at the screen bottom.
Due to the inability of KK to resize or to move anything within the KK3.2.0 plugin window/view, there's subsequentially no way to make related plugin controls visible (or to make use of such a plugin as it was originally intended by the vendor). NI really gave all of us the impression that HiDPI settings for Windows have already been implemented properly since KK3 was launched; but obviously that information was not correct. Sorry, but this is really a mess!
@Matthew_NI :
Can you please check and fix those errors? Thanks.
Btw., I just saw in the KK3.2.0 release notes that NI has obviously "fixed" some HiDPI issues since the previous KK version. Well, maybe exactly this circumstance has caused the new display issues which I just reported above. I'm also very sad about the fact that there's currently no single sign from NI, proving that you'll keep your promise to bring back most of the abandoned KK2 functionalities. I'm really loosing my hope.
