The following steps show that a new client can
connect and enable himself as a new driver even when
another driver is already driving the session.
-> User A connects to server
-> User A clicks Drive button
-> User B connects to server (same as above)
-> User B clicks Drive button
This results in User A's Drive button graying out
making User B the new driver. Once User B releases
the Drive control, it appears as if User A has become
the driver again, but the changes in his editor are
not getting synced over to User B's. User A has to
click the Drive button a few time to be able to gain
back real control of the drive.
If there's already a driver in motion, shouldn't a
new person joining the session be forced as a
navigator?
Thanks,
Jenny