Thank you for replying, it actually wasn’t the steam overlay I was referring to specifically - I’m not saying support for it should continue forever, just that issues with the alternative export options should be addressed before NW.js is sunset. Some of these seem challenging, e.g. github.com/MicrosoftEdge/WebView2Feedback/issues/4960 and might seem like small caveats but are very important to devs.
Either way thanks for midi support very cool!
Very worrying to see the end of NW.js support on the horizon, especially when community concerns over WebView2 seem to have been (so far) ignored. The worst case scenario is an "ask microsoft" or "complain to Steam" attitude towards WebView-Steam compatibility issues which will force many developers to a new engine. I've never really understood why WebView2 is referred to as an "in-house" exporter in the first place.
Member since 19 Dec, 2018