开云体育

Here's my current plan for coping with the various weird and wonderful things that decoders do when you write to CV1. Comments would be very welcome. Would this really solve the problems that people

(About hslider/vslider in a pane in a the decoder file itself) I've tried a couple examples of this in 1.0.6 and didn't see it fail. If you have an example file around, would you mind sending me a

At 11:51 PM +0200 9/8/02, Sip Bosch wrote about the possibility of making parts of the decoder definition condition on the version number. We could add a "minversion" to the individual variables. The

At 12:30 PM -1000 9/8/02, Jim Buckley wrote: >A possible bug in the Sountraxx DSD150 Diesel programmer's Function Mapping >screen. I wasn't able to confirm this on any other programmers -- I

-----Oorspronkelijk bericht----- Verzonden: vrijdag 13 september 2002 15:49 Aan: jmriusers@... Onderwerp: [jmriusers] User interface for "ops mode programming" I'd like to ask

I think I've fixed this. I didn't see a decoder file that defines a speed-table smaller than 28, so I hacked one together for a test. Do any decoder files need updating before I put this change

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.

<<rubbing my hands in gleeful anticipation... >> Hmmm... A good idea, certainly makes sense. Only _potential_ reason not to would be so that "visiting locomotives" could be programmed quickly, but

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

A possible bug in the Sountraxx DSD150 Diesel programmer's Function Mapping screen. I wasn't able to confirm this on any other programmers -- I was especially hoping someone could check a DSD150 Steam

Bob, It is a pleasure working with DecoderPro. Not only are new loco's easily programmed but the possibility of saving what one has done makes it a tremendous tool. Re 2 No, not yet. We've talked

Thanks for going through it so carefully, and for taking the time to write. This is a bug, thanks for catching it. No, not yet. We've talked about that, but haven't come up with the right way to do

Bob, Allow me the following remarks and implicit questions; 1. If the number of entries in the speedtable is less then 28 (i.e. - entries="15") it is not shown accordingly on the speedtable

Had a quick look through the revised document and must say you've made some excellent changes. Great Work! Bob explanations, pretty V1.0.7... if

OK... Spelling corrected, incorporated Programming Mode explanations, and reformatted things so that all the graphics are in a separate folder so I don't get confused so easily... "Nuff. I'm

It's been so long since I thought about this stuff I've probably got it wrong. The two really old (pre-DCC standard!) Lenz decoders I have installed in the boxcab (#36) and the MDC Consolidation

You're doing a great job Joe, maybe a double barrel 10 gauge :). Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief system NMRA Life member #2623 Member SFRH&MS

Only in a very simplified form. Most users don't need to know _why_ something is, just how to use it and when. For me, having enough information to write clear instructions is important. I _think_

On MacOS X, Windows and Linux, the size of some of the fonts is shrunk to make that page fit better. Unfortunately, the method used to shrink fonts isn't available on original Macintosh and OS/2.

So in place of the existing line of radio buttons, the identification panel and the main (tabbed) programming panel would have a bottom line that looked like Paged programming mode