Working natively on Windows 10 #4
Description
Currently the standalone application builds on windows, but when loaded the UI for instruments do not load.
The issue turns out to be that on Windows 10, Edge is used, if the feature is enabled, which is necessary to use any modern JS. It seems that unlike web-kit on Mac OS and Gtk-webkit2 on Linux, Edge has some funny behavior with respect to dynamically loading iframes. Many of the current UIs call directly into loaded JS for communicating with the hosting process, using a function called evoke, without indexing via the parent.
In Edge this does not seem to work!
It is unclear to me if this should always work or is just an extended feature of Web-kit. Anyhow the fix for this issue is to use the parent, the main index page that dynamically loads an instruments UI, to communicate with the underlying host. In truth this seems like a more robust abstraction anyway and so moving all UIs to this model seems a valid approach.
I've prototyped this approach with Nuke synth to use this approach and it is now working as expected.