Skip to content

Conversation

@McGiverGim
Copy link
Member

To be in the same line that betaflight/betaflight-configurator#1982

Maintaining the Chrome version produces confuse code. I've tested it under NW in Windows, and did some tests too under Chrome in Windows. All seems to work, but who knows...

@McGiverGim McGiverGim force-pushed the use_nw_window branch 3 times, most recently from 7d74298 to 7705ca6 Compare June 23, 2020 13:16
"version": "3.5.0",
"main": "main_nwjs.html",
"bg-script": "background.js",
"main": "index.html",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need "chromium-args" : "--disable-features=nw2" here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that not. If I remember correctly, we added this to the Configurator because it had problems opening/saving files to disk. The Blackbox must use something different because it seems to be working. At some moment we need to revisit the Configurator part.

@mikeller mikeller added this to the 3.6.0 milestone Jul 5, 2020
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 6, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants