Planned for Future

2.9.1 and 3.+ on Same Machine issue

So this is an interesting problem that isn't really a bug, but just something that I think will need to be dealt with eventually. 

With 2.9.1 and 3.0 on the same machine (Nomad on PC), if 2.9.1 is accidentally (or sometimes purposefully) opened in client mode, while connected to a network where 3.0 is the master, the Nomad PC machine after trying to connect, tries to update to 3.0.

While this is previously expected behavior, now that nomad machines can have both 2.9.1 and 3.0, I would expect instead of trying to update automatically, that 2.9.1 search to see if a newer version is already installed instead of auto-update.

cjLights
Parents

  • Hi all.  Interesting discussion.  We totally get this issue - and there are a handful of different solutions to pursue.    In addition to what is proposed here, we could also pop a dialogue on connection indicating the software version in use on the system when a mismatch is sensed.  That same dialogue could be used to indicate language conflicts.       So the concern is noted, disposition of exact solution TBD (along with a time frame).  And yes, as expected, none of this would be possible on any software released prior to the software to support the solution being released. 

    Thanks!!

    s

Comment

  • Hi all.  Interesting discussion.  We totally get this issue - and there are a handful of different solutions to pursue.    In addition to what is proposed here, we could also pop a dialogue on connection indicating the software version in use on the system when a mismatch is sensed.  That same dialogue could be used to indicate language conflicts.       So the concern is noted, disposition of exact solution TBD (along with a time frame).  And yes, as expected, none of this would be possible on any software released prior to the software to support the solution being released. 

    Thanks!!

    s

Children
No Data

www.etcconnect.com