MIDI plugin; Improved CPU profiler; Tilemap brush editor improvements & more.
Steam has fallbacks that show the actual Steam UI instead of an in-game overlay, so Valve have an alternative implementation there that WebView2 uses. As NW.js is essentially unmaintained, may well be retired at some point, and integrating custom native code in NW.js for things like Steam integration is extremely difficult and requires constant maintenance (and has finnicky version matching requirements), I don't think it makes sense to continue to support NW.js just to get the in-game overlay instead of the fallback.
It's not like we've ignored the community over this - we have in fact gone to great lengths to try to support the in-game overlay, but various problems and limitations with Valve's implementation make it infeasible. So while it is unfortunate we can't support that, if you want it supported the best thing to do is contact Valve, as it seems only they can solve the problem.
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!