+1 on the window focus issues. Interacting with the harp where I intentionally expect to interact with a screen UI, browse settings should launch eigenbrowser if not already running. If already running it should bring the window to the foreground. If we are usig the harp to interact with a UI which we are then it should have a similar effect to what a mouse would do as far as focusing.
Same with opening a plugin window, that window should be focused to foreground. Even the status windows for example when loading a preset, open in back of the main window which is just bizarre because usually in any UI framework, these types of windows are very easy to make modal. I understand that EigenBrowser is running in a different process than eigenD but since they do communicate with each other, it should be possible to also focus the window properly. Remember the window positions and size, etc...
These little things make a big difference.
One thought I had would be to create a screen overlay window that pops up when a setting is being changed and can be made very large. For example, when changing a volume setting with the harp, the value being changed would be displayed very large in floating system tray-type window. The kind that floats above everything else, is semi-transparent and maybe even dims the rest of the screen while the value changes.
This would be very helpful on stage or even studio, where you are not sitting right next to your laptop squinting at some value and definitely not trying to find and bring eigenbrowser to the foreground.