开云体育

I'd like to ask about how the user should see "ops mode programming" in DecoderPro.

For technical reasons, it would be significantly simpler to code it (at least for today) if the program could assume that a Roster entry already existed for a decoder accessed in Ops Mode.

To do that I suggest:

a) The DecoderPro main page now contains a "Program Locomotive..." button and a "Quit" button. The "Program Locomotive..." button would be renamed to "Program Decoder on Programming Track..." and continue to function the exact same way. "Quit" would remain unchanged. A new "Program on Main Track..." (PMT) button would be added, see below. (These names are wordy and obscure. Can somebody suggest a better way to capture this difference that's not system-specific?)

b) Pressing the PMT button pops a new screen similar to the top-half of the existing ident screen. There's a selection box to pick a roster entry, and an open-programmer button. But there's no ident button(s), and no decoder-selection tree.

So you click "Program on Main Track ...", select the loco from your existing ones, and go.

If you don't have a roster entry for a loco, you should probably put it on the programming track and "Read All" to create one. But you could just create a dummy entry with the right address, but without ever hitting a read or write button, and then use that for ops mode.

Does this sound OK to people?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

--- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote:

I'd like to ask about how the user should see "ops mode programming"
in DecoderPro.

<<rubbing my hands in gleeful anticipation... >>

For technical reasons, it would be significantly simpler to code it
(at least for today) if the program could assume that a Roster entry
already existed for a decoder accessed in Ops Mode.

Hmmm... A good idea, certainly makes sense. Only _potential_ reason not
to would be so that "visiting locomotives" could be programmed quickly,
but I don't see that as being a frequent need.

To do that I suggest:

a) The DecoderPro main page now contains a "Program Locomotive..."
button and a "Quit" button. The "Program Locomotive..." button would
be renamed to "Program Decoder on Programming Track..." and continue
to function the exact same way. "Quit" would remain unchanged. A
new "Program on Main Track..." (PMT) button would be added, see
below. (These names are wordy and obscure. Can somebody suggest a
better way to capture this difference that's not system-specific?)

Hmmm... how about radio buttons? Text saying "Program locomotive on:"
then radio buttons labeled "Programming Track" and "Layout", then use a
"Select Locomotive/Decoder" button to open the appropriate window.

b) Pressing the PMT button pops a new screen similar to the top-half
of the existing ident screen. There's a selection box to pick a
roster entry, and an open-programmer button. But there's no ident
button(s), and no decoder-selection tree.

So you click "Program on Main Track ...", select the loco from your
existing ones, and go.

If you don't have a roster entry for a loco, you should probably put
it on the programming track and "Read All" to create one. But you
could just create a dummy entry with the right address, but without
ever hitting a read or write button, and then use that for ops mode.

Does this sound OK to people?

Well, It's seems to me that one of the biggest reasons for OPS mode
programming is to play with speed matching... sooo...

How about _this_ approach?

Allow 2 decoders to be open at once, in "layered" windows. This would
let you twiddle both speed curves.

Maybe this ought to be a "special case" programmer, and use only the
MinV, MidV, MaxV, forward and reverse trim, and speed curve pane (split
horizontally for two locomotives) and allow manual entry of the
address.

Bob-
This sounds excellent to me. How close are you to having the code done? I
would like to try to get a Racetrack like program added to the system, and
the Ops mode would be essential. Unfortunately, I won't have any time for
that until into October.
David

Bob Jacobsen wrote:

I'd like to ask about how the user should see "ops mode programming"
in DecoderPro.

For technical reasons, it would be significantly simpler to code it
(at least for today) if the program could assume that a Roster entry
already existed for a decoder accessed in Ops Mode.

To do that I suggest:

a) The DecoderPro main page now contains a "Program Locomotive..."
button and a "Quit" button. The "Program Locomotive..." button would
be renamed to "Program Decoder on Programming Track..." and continue
to function the exact same way. "Quit" would remain unchanged. A
new "Program on Main Track..." (PMT) button would be added, see
below. (These names are wordy and obscure. Can somebody suggest a
better way to capture this difference that's not system-specific?)

b) Pressing the PMT button pops a new screen similar to the top-half
of the existing ident screen. There's a selection box to pick a
roster entry, and an open-programmer button. But there's no ident
button(s), and no decoder-selection tree.

So you click "Program on Main Track ...", select the loco from your
existing ones, and go.

If you don't have a roster entry for a loco, you should probably put
it on the programming track and "Read All" to create one. But you
could just create a dummy entry with the right address, but without
ever hitting a read or write button, and then use that for ops mode.

Does this sound OK to people?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)


To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...



Your use of Yahoo! Groups is subject to

--
David Harris
OmniPort Home Page:
Discussion egroup:
Swiki:

-----Oorspronkelijk bericht-----
Van: Bob Jacobsen [mailto:Bob_Jacobsen@...]
Verzonden: vrijdag 13 september 2002 15:49
Aan: jmriusers@...
Onderwerp: [jmriusers] User interface for "ops mode programming"


I'd like to ask about how the user should see "ops mode programming"
in DecoderPro.

Does this sound OK to people?

OK with me.

Sibbo


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

At 2:42 PM +0000 9/13/02, Joe Ellis wrote:

Well, It's seems to me that one of the biggest reasons for OPS mode
programming is to play with speed matching... sooo...

How about _this_ approach?

Allow 2 decoders to be open at once, in "layered" windows. This would
let you twiddle both speed curves.

Maybe this ought to be a "special case" programmer, and use only the
MinV, MidV, MaxV, forward and reverse trim, and speed curve pane (split
horizontally for two locomotives) and allow manual entry of the
address.

More than one ops-mode programmer can be open at a time, so that's no problem except for perhaps screen space. It might be useful to create a programmer format that's really svelte so you can fit 2 or 3 or 4 on the screen at once.

Right now, you can actually open more than one programmer screen at the same time. They work independently of each other, which is confusing, but they do work. Once I make these changes to include ops-mode, I was going to limit it to only one service-mode (e.g. programming track) programmer window at a time.

Bob

--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

No! I like having more than one programmer window open at a time. Then I
just pop up the one I need at the moment -- much faster and convenient than
reopening them, especially in a club situation, where you may be programming
several decoders recurrently.

For a 'racetrack' mode, you need to be able to step through the speed tables
of both locos concurrently and adjust each speed table entry for one (or even
both) loco. I think the stepping through the speed tables doesn't require
linking the two op-mode programming pages, but would be convenient. I had
envisioned a single page with the spped table of the second loco, and some
buttons for stepping up and down the speed tables.
David

Bob Jacobsen wrote:

At 2:42 PM +0000 9/13/02, Joe Ellis wrote:

Well, It's seems to me that one of the biggest reasons for OPS mode
programming is to play with speed matching... sooo...

How about _this_ approach?

Allow 2 decoders to be open at once, in "layered" windows. This would
let you twiddle both speed curves.

Maybe this ought to be a "special case" programmer, and use only the
MinV, MidV, MaxV, forward and reverse trim, and speed curve pane (split
horizontally for two locomotives) and allow manual entry of the
address.

More than one ops-mode programmer can be open at a time, so that's no
problem except for perhaps screen space. It might be useful to
create a programmer format that's really svelte so you can fit 2 or 3
or 4 on the screen at once.

Right now, you can actually open more than one programmer screen at
the same time. They work independently of each other, which is
confusing, but they do work. Once I make these changes to include
ops-mode, I was going to limit it to only one service-mode (e.g.
programming track) programmer window at a time.

Bob

--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)


To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...



Your use of Yahoo! Groups is subject to

--
David Harris
OmniPort Home Page:
Discussion egroup:
Swiki:

--- In jmriusers@y..., "Joe Ellis" <filker@m...> wrote:

<<snip>>

How about _this_ approach?

Allow 2 decoders to be open at once, in "layered" windows. This would
let you twiddle both speed curves.

Maybe this ought to be a "special case" programmer, and use only the
MinV, MidV, MaxV, forward and reverse trim, and speed curve pane (split
horizontally for two locomotives) and allow manual entry of the
address.

Here's a _very_ rough graphic of the kind of approach I'm talking
about:



I just pasted this together out of some of the screen shots I did for
the manual.

How about having basic throttle functions available _on_screen_ ? Just
Forward, Reverse, and _28_ speed steps. (the only ones you can adjust
on the speed tables). It would make programming easier by not having to
go back and forth between keyboard and throttle all the time.

While we're shooting the moon, would it be possible to have a "link
throttles" option, so that both locomotives got the same speed
commands? I'm not sure that OPS mode programming of MU'd units might
not defeat the purpose...

Hi-
This is very similar to what I had proposed about a month ago! See: [Image]
at the bottom of the page.
David

Joe Ellis wrote: