开云体育

David:

Thanks. It installed OK when I simply dbl clicked the jmri...exe.

New question:

Under "Preferences", which box should be checked in the "GUI" line.
I run Windows 98, should I check the Windows box?

Thanks again,

Jim Hanna

Hi Bob:

What is the command to install the new jmri.1.0.1.exe from a CD? I have tried E:\startup & e:\install but get error msg.

Jim Hanna
El Cajon, CA

Just execute the file (it is an exe afterall), and it will do an install.
David

Jim Hanna wrote:

Hi Bob:

What is the command to install the new jmri.1.0.1.exe from a CD? I have tried E:\startup & e:\install but get error msg.

Jim Hanna
El Cajon, CA




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:

Oh, what a relief -- I thought I was just being an idiot ;-)
Thanks for all you've done so far!
David

Bob Jacobsen wrote:

At 8:07 AM -0700 7/29/02, David Harris wrote:

Hi-
When I select 'new panel' on Win98, I get a blank panel, but no Panel Editor
Window???

Yes, that's the symptom for the broken install. Sorry. I'll get it
fixed, hopefully this evening.

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:

At 8:07 AM -0700 7/29/02, David Harris wrote:

Hi-
When I select 'new panel' on Win98, I get a blank panel, but no Panel Editor
Window???

Yes, that's the symptom for the broken install. Sorry. I'll get it fixed, hopefully this evening.

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

Hi-
When I select 'new panel' on Win98, I get a blank panel, but no Panel Editor
Window???
Thanks, David

Alex Shepherd wrote:

*) Control panel tool, see

Bob have you got a sample config file that has a layout (or parts)
configured? I had a play around in the weekend but didn't get very far and
having something done already would help

Alex


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:

At 11:38 PM -0700 7/28/02, Bob Jacobsen wrote:

I've uploaded a new test installer for Windows. Let me know if
anybody wants a .zip file for Linux or Macintosh.

...

*) Control panel tool, see

Unfortunately, the new control panel tool in the 1.0.1 installer doesn't work. I don't quite understand this yet. It works on a test machine, but if you download the installer onto a clean machine, the panel editor crashes on startup. The installer seems to not create a completely functioning program. The panel editor does need some new stuff, so that's where I'll look first, but it may take a while to figure out.

The rest of the program seems OK, so if you're only interested in the DecoderPro updates it should work fine for you.

I'll look at this as soon as a I can, but it probably won't be until this evening.

I'm sorry for any inconvenience.

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

At 1:22 PM +0000 7/29/02, Lab_Monkee wrote:

On installing the latest version, is it wise to "remove" the
old version first from MS Windows, or can you install directly over
it?

It should be OK to just run the new installer. The "remove JMRI" option in the Start menu is there mostly for people who decide they're not interested in the program at all. It will reclaim some space for them.

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

Hello,

On installing the latest version, is it wise to "remove" the
old version first from MS Windows, or can you install directly over
it?

Jose


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

I've uploaded a new test installer for Windows. Let me know if
anybody wants a .zip file for Linux or Macintosh.

Features:

*) Fixes to TCS decoder definition, thanks to Jon Miller. Fix minor
typos in other labels.

*) DecoderPro speed table now has editable numbers, thanks to Alex

Shepherd.

Speed table also has three new buttons for setting various curves.

*) New "speedometer" tool in JmriDemo program (development menu).

I'd

love to know if it works for LocoNet users...

*) Control panel tool, see

*) Fixes to serial port error checking and recovery; you'll now get

a

dialog box for certain easy errors.

*) Roster file handling improved; now remembers the last directory
you used (until program is restarted), starts in the user

preferences

directory.

Some of the error handling code is experimental, and feedback would
be greatly appreciated.

The installer can be downloaded from



or the usual SourceForge mirrors.

Bob

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

*) Control panel tool, see

Bob have you got a sample config file that has a layout (or parts)
configured? I had a play around in the weekend but didn't get very far and
having something done already would help

Alex

I've uploaded a new test installer for Windows. Let me know if anybody wants a .zip file for Linux or Macintosh.

Features:

*) Fixes to TCS decoder definition, thanks to Jon Miller. Fix minor typos in other labels.

*) DecoderPro speed table now has editable numbers, thanks to Alex Shepherd.
Speed table also has three new buttons for setting various curves.

*) New "speedometer" tool in JmriDemo program (development menu). I'd love to know if it works for LocoNet users...

*) Control panel tool, see

*) Fixes to serial port error checking and recovery; you'll now get a dialog box for certain easy errors.

*) Roster file handling improved; now remembers the last directory you used (until program is restarted), starts in the user preferences directory.

Some of the error handling code is experimental, and feedback would be greatly appreciated.

The installer can be downloaded from



or the usual SourceForge mirrors.

Bob

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

Hello,

I just wanted to say that I am a new user, and am very pleased
with this software. I am eager to check out the next update with the
numerical speed table, and also will a future release include the
DZ121, or is there an equivalent already on the list?

Thanks,

Jose

Hello,

Just wanted to say I am a new user and am very pleased with this
software. I'm eager to see the next update with the numerical display
speed table. Also, will the Digitrax DZ121 be included in a future
release or is there an equivalent already on the list?

Thanks!

Jose

No problem Bob. Working with Robin the problem is fixed. It turned out
that the first two function lines said "forward" instead of "forward" then
"reverse". Once that was changed then the lights worked correctly.
I really wish I could help with the programming but the time I spent on
that little problem convinced me "I'm not a programmer"<VBG>.

Yeah, debugging this stuff can be really frustrating...

Let me check to make sure. These lines in each light definition:

<enumChoice choice="Function on when loco going forward"/>
<enumChoice choice="Function on when loco going forward"/>

should really be:

<enumChoice choice="Function on when loco going forward"/>
<enumChoice choice="Function on when loco going reverse"/>

Is that right?

Bob

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

At 4:27 PM +1200 7/27/02, Alex Shepherd wrote:

> That sounds like a big improvement over the way I left it. Could you

commit those changes?

Done, I hope changing the field width from 4 to 3 did not break something
else...

Thanks. I'll run that through the tests for this weekend's update.

c) A new "Speedometer" tool, available under the Development menu in
the JmriDemo program. It times the interval between two input
sensors going inactive or active and converts that to scale MPH.
Still rudimentary, but I wanted to see how well it would actually
work. Note that senors only work with LocoNet now; NCE/Lenz feedback
is polled, and I don't have any code to do that.

Is this the begginings of what I was talking about a while ago about
automatically being able to calibrate your loco speed table so the the
throttle indicates scale MPH?

It is, but really only the beginning.

I don't yet understand how people will actually use something like this while programming. Any kind of iterative procedure to find the value for all 28 speed steps would take a _long_ time, and I'm not sure it's worthwhile. For a single value it could work, though I'm not sure how linear the typical locomotive is.

Mostly I'd like to play with it when I get some time on the layout, and encourage other people to do that too.

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

That sounds like a big improvement over the way I left it. Could you
commit those changes?

Done, I hope changing the field width from 4 to 3 did not break something
else...

Also I see you mention some buttons that set the curve to some preset

shapes

but they don't show up when I run the code. Maybe they are not checked-in
yet...

They work well

c) A new "Speedometer" tool, available under the Development menu in
the JmriDemo program. It times the interval between two input
sensors going inactive or active and converts that to scale MPH.
Still rudimentary, but I wanted to see how well it would actually
work. Note that senors only work with LocoNet now; NCE/Lenz feedback
is polled, and I don't have any code to do that.

Is this the begginings of what I was talking about a while ago about
automatically being able to calibrate your loco speed table so the the
throttle indicates scale MPH?

Alex

I've written a brief introduction to the new JMRI control panel tool:



Comments would be appreciated.

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

Hi Bob,

I just did a CVS update and run to have a look at the value boxes on top of
the sliders and yes the font is pretty small. Even when you set the value to
255 the text only fills about 2/3 of the box width.

I had a play around with the box and font size by tweaking the following
lines:

a) In the DecVariableValue constructor I changed:
_value = new JTextField("0",4);
to
_value = new JTextField("0",3);

b) In SpeedTableVarValue.getRep I changed:

float newSize = (v.getFont().getSize()+0.5f)/2.f;
to
float newSize = v.getFont().getSize() * 0.8f;

This gives me a font size of about 10 and it makes a space between the
sliders of about 1 mm so the page does not change much and makes the text
quite readable.

Looking at the code I'm not really sure what actually determines the width
of the text box and what I tweaked may not have made a difference as with
the above settings there is almost room for another character.

That sounds like a big improvement over the way I left it. Could you commit those changes?

Also I see you mention some buttons that set the curve to some preset shapes
but they don't show up when I run the code. Maybe they are not checked-in
yet...

Sorry, I was behind on checking in the source. I just committed a couple of things:

a) The buttons on the speed table

b) Convenience fixes to the roster menu filehandling so that it goes to a reasonable place when it opens the first time, and it remembers where you were later.

c) A new "Speedometer" tool, available under the Development menu in the JmriDemo program. It times the interval between two input sensors going inactive or active and converts that to scale MPH. Still rudimentary, but I wanted to see how well it would actually work. Note that senors only work with LocoNet now; NCE/Lenz feedback is polled, and I don't have any code to do that.

More to follow...

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

Hi Bob,

I just did a CVS update and run to have a look at the value boxes on top of
the sliders and yes the font is pretty small. Even when you set the value to
255 the text only fills about 2/3 of the box width.

I had a play around with the box and font size by tweaking the following
lines:

a) In the DecVariableValue constructor I changed:
_value = new JTextField("0",4);
to
_value = new JTextField("0",3);

b) In SpeedTableVarValue.getRep I changed:

float newSize = (v.getFont().getSize()+0.5f)/2.f;
to
float newSize = v.getFont().getSize() * 0.8f;

This gives me a font size of about 10 and it makes a space between the
sliders of about 1 mm so the page does not change much and makes the text
quite readable.

Looking at the code I'm not really sure what actually determines the width
of the text box and what I tweaked may not have made a difference as with
the above settings there is almost room for another character.

Also I see you mention some buttons that set the curve to some preset shapes
but they don't show up when I run the code. Maybe they are not checked-in
yet...

Alex

How about this Bob,

How About a magnifying feature to work with the small point size.

When one clicks on a slider adjustment or places the pointer on the small
numerical box above it, the numerical box grows larger (even overlapping
other adjacent boxes somewhat if necessary) such that the number become
very visible and easy to change. When one clicks on another slider,
numerical box, anywhere in a neutral window pane area or finishes typing
in the number and hit return, the box that has grown will now shrink back
to normal size showing the old or new value as required.

Another Idea is to have a dedicated numerical box that has a very
readable font size on the window pane some place above the speed table.
When one clicks on any slider, the box is updated to reflect the value
that correlates with that slider. When no slider is selected, the box
goes blank. Data entry is also done with this box. As before when a
slider is selected, the value in the box can be changed by clicking on
the box, making you entry and hitting return. After hitting return, the
box goes back to being just a display box. Of course sliding the slider
will dynamically update both the small font box and the big box. The
purpose of clicking on the box to perform data entry is to prevent
accidental data changes. The changes must be deliberate. Of course your
table graphical editing automation tools will work without clicking the
box.

Sorry to be so long getting back to this topic.

I've made a couple of attempts at getting the digits to line up
vertically, and there doesn't seem to be a clear-cut way to do it.
Perhaps somebody else knows how and is willing to contribute that
code.

Instead, I've added boxes above the sliders and adjusted the font in
them so that they fit. On some platforms, this results in quite
small type (e.g. on Linux, you get 5 point characters); still
readable, but small. You can type the numbers in there directly and
the slider will adjust, or you can move the slider until the number
is right.

I'll put out a test version over the weekend.

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

Best Regards,

Mark Gurries
Linear Technology
Power Supply & Battery charger Applications Engineer/Manager
---------------------------------------------------------
Model Railroad Club and NMRA DCC presentations are at:

--------------------------------------------------------
Audio Enthusiast (Love SAE equipment)


----------------------------------------------------------