David Baker
David Baker
As @robintown points out, if we're doing device name matching in EW to get the right preview, we may as well just pass the chosen devices over by device name...
Separating the two into different things could work quite well
Oh, we should remember to include instructions to route everything to index.html
Is it just those two devices in the call?
It's very possible there's something that needs to be optimised here - a CPU profile from the browser's dev tool could be very useful if anyone experiencing this is able...
Oh, only happens if the window isn't very tall
Actually I don't think this is a regression (although it's not ideal that the walkie-talkie mode interface needs most of the height of a full HD monitor to display properly).
This is done automatically by the release script (adds it for the the release then removes it again for development) so that, on the develop branch, the default entry point...
Sounds like a renderer process crash. We'd need to hook up native crash reporting to figure out what's going on, or it might fix itself with an upgrade of electron.
I've increased the timeout on the flush in the above PR, but I can't repro the failure so I'm struggling to see how it would be possible for the code...