I've been following this discussion with lots of interest.
I like the idea of allowing adding a connection letter box (or something similar) to throttles, programmers, etc. _provided_ its entry is only required if there are multiple connections. I think that is what Dick was urging below.
The advantage of 1), versus what we do now and 2. below, is maximum flexibility for the user with multiple connections. It would also be very similar to the way we handle sensors and turnouts now--they can be spread over multiple systems.
I agree with Rodney and Dick on naming conventions.
My 2 cents.
On Jan 28, 2009, at 11:42 AM, Dick Bronson wrote:
I see two ways to do this. Either; 1. add a connection letter box to
throttles, programmers, etc. or, 2. add function check boxes in the
connection windows. 'Service ', 'Ops ', 'Throttle ', etc.
I think I prefer #1. The first time you open a throttle for example, it
would default the connection type letter to the main layout connection.
(NOT the last one in the list like it does now) If you were controlling
two systems from one JMRI session, then you could over ride the
connection letter as required. The same would be true when opening each
programmer window. (Service mode or Ops mode) Remember our example
above? The service mode window would be connected to the PR3, but the
OPs mode window would be using the LocoBuffer-USB.
The problem with #2 is that you could not have one throttle on one
connection and a second throttle on a different connection.
The beauty of all this is that for the user with a simple system with a
single point of interface, all the defaults would automatically let his
JMRI work. For the train store dealer that has several systems setup in
a display he could show his customers how they compared simply by
selecting what interface he wants to connect with. For the person that
wants to be able to use one NCE unit to program locos at the same time
his layout is running with another, he could do it without needing to
run two copies of JMRI.