--- In jmriusers@y..., jerry snyder <jerrys@c...> wrote:
Really a nice work! I have just printed it and am sure it will be helpful
in mastering Decoder Pro.
Umm... I didn't really think anyone would want to actually print this whole thing out - rather, just use it online. When we get the initial kinks worked out I'll try to do an archive file that has the whole thing in it so it can be downloaded and accessed off your own computer instead of over the net. That will speed things up considerably!
I noticed in printing that:
The link to using Decoder Pro also includes the Using the Basic Programmer
section. I almost printed this section twice.
Probably because they're on the same "page"... I used "Targets" to go to the appropriate key points. Should I break this out onto its own page? I thought it made more sense this way...
The last screen shot, Setup and Roster Panes, is too wide for the
document. The right portion is clipped.
The screen shots for the Comprehensive Programmer are big and wide. (around 830x598, give or take a pixel or two) There's a lot of "white space" (actually, gray space) in the screens, but I didn't want to potentially confuse folks by changing the way the screen looked. If a screen is clipped, there's a scroll bar in it to get to the hidden part. (probably ought to add that to the manual, too...)
Can your browser print at, say, 85-90% size? That should solve the problem.
The most extreme example of overly wide graphics is the Speed Control page. I _did_ scale the shots of the effects of the "curve" buttons down because no essential information was lost - the shape of the curve was still evident. If I scale the others, though, it makes it impossible to read the text.
Now to get to what was asked about typo's etc.
BTW is filker@m... the Joe Ellis recently of Orlando N'Trak fame?
That's me! What, you didn't recognise the BARR roadname in the roster screen? <<grin>> Hi, Jerry!
Cheers
jerry snyder
Orlando, FL
