[Geoff Bacon]

Hi Mike

Double clicked companion on W11 and, as nothing obvious was happening, double clicked it again.
Ended up with two companions running.

I gave you some code previously to prevent this and I'm guessing you haven't included it in the companion rewrite
Note: I'm still running 4.1.2 Companion (and MS 3.9.7)

Keep up the good work

Cheers
Geoff

[BRX]

Hi Mike. Though this is a bug post from Geoff it gave me an idea I'd like to discuss.

Is it complicated to allow 2 instances of the companion, each connected to a different client (probably just makes sense over wlan)?

I'm thinking whether the existing companion can be extended to use it for direct comparing contents/copying/moving between 2 companions/clients.
It would be nice for occasions where a whole sync is to much or not wanted for other reasons.

[Zubersoft]

I'm not able to have two instances with the current networking code because they will both want to bind to listen for network messages on the same port, so the 2nd instance errors out as two applications can't both listening to that same port. I already plan on switching to DNSSD for the device discovery, so in theory that might get around that issue. I also haven't checked it, but is it possible to use Connection->Manual WiFi Connect with two instances up to connect to different devices?

Mike