Real-time sharing waypoints and routes on 2 devices?

[rgleason]

Perhaps for the time being use a batch file to copy the Navobj.xml file
http://www.cruisersforum.com/forums/...ml#post2592249

[MV Wanderlust]

Originally Posted by rooiedirk

My 2c.
I can imagine a plugin with a server and client mode. If on the server the Btn is clicked you get a popup window where you can choose what to synchronise (route waypoints tracks layers charts etc) and at the same time a UDP message is send on all network devices to clients to report itself.
Due to the reports we can also add a list of clients where we can choose with witch to sync. Then OK and a tcp connection with each client for the syncing. This leaves all control at the server.


On the client side there should be an acknowledge window to allow changes. I definitive don't want changes to a route without me approving it. However there could be a switch to turn it off.



I don't think we should try syncing an active track.

That sounds like a useful plugin!

[rgleason]

There are four Tracker Tasks which have a total of 16 votes in the Vetted Feature requests. Only "Alarm Depth has more (19) votes.

I've combined these into one task FS#2205
and added Dirk's description too. I think Dirk's description of operation above is excellent.

[Unregistered-1]

you might ssh -X to one machine and run multiple instances on remote displays. This would be trivial and a quick test here shows success.

Might need a lead developer to comment on the wisdom of doing that however...

For those who don't know what I just said - you can easily connect to a remote Ubuntu machine and run apps remotely - all this is built in natively and runs instantly without question. Putty X-forwarding logins can be automated with SSH keys. Once this is setup it works invisibly. You will need a super-solid wireless network to pull a stunt like this however, perhaps a professional 5GHz AP, or else wire it.

[rgleason]

Real time sharing is unlikely to happen. Sharing from nav station to cockpit station is implemented with 5.8.2. See discussion https://github.com/OpenCPN/OpenCPN/d...omment-5952100