开云体育

At 8:46 PM -0800 11/2/02, Michael Mosher wrote:

Also, how do I get the loco table to be sorted in Ver 1.1?

That should happen automatically. I'm a little surprised if it's not being sorted, but a bug like that is certainly possible.

Note that it's a "lexical" sort. That means the sort-order is:

1
A
B
C
a
b
c

Note that all the upper-case letters are before all the lower case letters.

The "Java Human Interface Guidelines" recommend this order, but I really don't know why. Does anybody? If people would prefer the usual alpha order (AaBbCc etc), let me know. It's easy to change.

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

Bob Jacobsen wrote:

At 8:46 PM -0800 11/2/02, Michael Mosher wrote:

Also, how do I get the loco table to be sorted in Ver 1.1?

That should happen automatically. I'm a little surprised if it's not
being sorted, but a bug like that is certainly possible.

Note that it's a "lexical" sort. That means the sort-order is:

1
A
B
C
a
b
c

Note that all the upper-case letters are before all the lower case letters.

The "Java Human Interface Guidelines" recommend this order, but I
really don't know why. Does anybody? If people would prefer the
usual alpha order (AaBbCc etc), let me know. It's easy to change.

I vote that one use the usual Alpha order for it easier to understand and
is more importantly, more natural in terms of expectations.



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)

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

Note that all the upper-case letters are before all the lower case letters.

The "Java Human Interface Guidelines" recommend this order, but I
really don't know why. Does anybody? If people would prefer the
usual alpha order (AaBbCc etc), let me know. It's easy to change.

I vote that one use the usual Alpha order for it easier to understand and
is more importantly, more natural in terms of expectations.

The Java guidelines were probably written by unix geeks, rather than humans.
(Insert smiley face - I confess to being a unix geek) I too suggest simple
alpha ordering. In fact, it would be a good idea to completely ignore alpha
case in roster entry names. ie.: SoundTraxx == soundtraxx == SOUNDTRAXX...
This would keep me from creating a roster entry named xyz-123 and XYZ-123 for
the same locomotive/decoder.

Mike Davison

The "Java Human Interface Guidelines" recommend this order, but I
really don't know why. Does anybody? If people would prefer the
usual alpha order (AaBbCc etc), let me know. It's easy to change.

How about forcing to all key names to UPPER, lower case or do a case
independant sort. Then you don't have to worry about having the same name
but with different case causing problems with Windows file names. UNIX (and
your Mac) knows about the differences between upper and lower case names but
Windows thinks they are the same.

Does DecoderPro do anything to avoid upper/lower case filename issues now
for filenames? What happens if I save a decoder under a different case
name - do both entries try and share the same filename?

Alex

At 2:27 PM -0800 11/4/02, Mike Davison wrote:

The Java guidelines were probably written by unix geeks, rather than humans.
(Insert smiley face - I confess to being a unix geek) I too suggest simple
alpha ordering. In fact, it would be a good idea to completely ignore alpha
case in roster entry names. ie.: SoundTraxx == soundtraxx == SOUNDTRAXX...
This would keep me from creating a roster entry named xyz-123 and XYZ-123 for
the same locomotive/decoder.

OK, done. It'll be in the next test version released, and is in CVS now.

At 11:59 AM +1300 11/5/02, Alex Shepherd wrote:

Does DecoderPro do anything to avoid upper/lower case filename issues now
for filenames? What happens if I save a decoder under a different case
name - do both entries try and share the same filename?

It (is supposed to) notice that the file already exists and pick a different name. It's also supposed to prevent you from changing the ID of a roster entry to one that already exists. I haven't really tested that in a long time, however.

Bob


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