nerdCopter

i always wondered why command-line `--new-window` never worked. now with deprecation, presumably non-fixable.

- i don't like this solution; however, it seems to work. - NW.js and ffmpeg may be un-syncronized with this. - @ctzsnooze , can you test the executable-package created by...

i found some issue with any logic for when using gulpfile to retrieve the OS version (kernel). it is built on modern OSX (kernel), therefore will still choose modern NWjs,...

the future is now :smile: :frowning_face:

saw some NWjs issue tracker comments alluding to custom universal packages , but this is just more effort / maintenance :( finding some more stuff. maybe [only] a newer `nw-builder`...

thank you @ikherty . sorry @haslinghuis @ctzsnooze , i don't know a way to import different ffmpeg versions depending on NWjs version :frowning_face: . maybe a BASH script at build-time...

user reported custom defines worked, FWIW. Still no clue about LDO.

legacy hardware and defunct vendor, just making it work for the single user that mentioned it -- can be merged without regret.

@coderabbitAI, deep analyze the issue and the source-code as it pertains to the issue. it is probably easier to analyze the `4.5-maintenance` branch rather than `master`.

not a fan of "non-bracketed" as well. seems some are in the existing unchanged code. recommendation @haslinghuis ?