Bug 8143 - Scrolling terminology/settings are mixed up
: Scrolling terminology/settings are mixed up
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.0.1
: All All
: -- normal (vote)
: 7.x
Assigned To: KDF
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-14 00:34 UTC by Jim McAtee
Modified: 2009-09-08 09:17 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
new strings (5.20 KB, patch)
2008-05-14 10:01 UTC, KDF
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2008-05-14 00:34:46 UTC
The scrolling terminology and/or the settings are a little mixed up.  The terms appear as follows for the three scrolling options under Player Settings > Display:

Single Line Scroll Rate/Pause/Pixels:
Double-Size Scroll Rate/Pause/Pixels:

"Double-Size" _is_ single line.  The information text, on the other hand, uses the wording "single-line" and "double-line" in its explanation.

__BUT__

The actual use of the options appears to be:

Single Line is used for multi-line font scrolling
Double-Size is used for single line font scrolling

That makes the information text for Scroll Rate wrong when it says "0.15 seconds is the default for single-line, 0.1 seconds for double-line".  It's actually 0.15 seconds for double-line (displayed on top) and 0.1 for single-line (the bottom setting).

Considering that there's also a "Threeline" font that uses the single line scrolling prefs, I'd suggest the following terminology for the same two settings in the same order as they appear now on the settings page:

Multi-line Scroll Rate/Pause/Pixels:
Single Line Scroll Rate/Pause/Pixels:
Comment 1 KDF 2008-05-14 10:01:17 UTC
Created attachment 3343 [details]
new strings
Comment 2 KDF 2008-05-29 13:22:03 UTC
adding Brian to cc.  awaiting target/approval (I need validation, dammit ;)
Comment 3 Brian Dils 2008-05-29 14:35:28 UTC
I agree with your suggestions for what its worth, makes sense to me...
Comment 4 KDF 2008-05-29 23:01:25 UTC
great, so all that's left is to know if this is something for 7.1, 7.0.2 or just 7.2 given that it needs new localisations from the translation group.
Comment 5 James Richardson 2008-06-02 09:47:23 UTC
KDF, please check in to 7.1 and QA will have a look at it, on the next daily build.
Comment 6 KDF 2008-06-02 10:42:11 UTC
change 20419
Comment 7 Jim McAtee 2008-06-04 21:53:25 UTC
I just tested this.  The terminology is fine, but the settings appear (in my mind) backwards.  "Single Line" settings appear to affect multi-line displays and vice versa.

I guess it lies with the logical interpretation of "single line" and "multi line" (formerly "double-size").  Does it refer to the font size, with "single line" meaning any of the smaller fonts that fit on a single line and with multi-line (double size) meaning a font using more than one line of the display?  Or does it mean the display itself, with single line meaning a display with a large, single line of text and multi-line meaning all the other display modes?

To my thinking, it's easier to think in terms of the number of text lines on the display.
Comment 8 Blackketter Dean 2008-06-05 07:47:13 UTC
How about:

Scroll Rate
Large Text Scroll Rate


Comment 9 KDF 2008-06-08 11:43:32 UTC
large text, change 20520
Comment 10 KDF 2008-06-08 12:06:12 UTC
and change 20521
Comment 11 James Richardson 2008-07-16 14:33:59 UTC
This appears to be addressed in

SqueezeCenter 7.1-21796
Controller 7.1 r2699
Comment 12 Chris Owens 2008-07-30 15:33:09 UTC
This bug has now been fixed in the 7.1 release version of SqueezeCenter!  Please download the new version from http://www.slimdevices.com if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 13 James Richardson 2008-12-15 12:32:35 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 14 Chris Owens 2009-07-31 10:21:25 UTC
Reduce number of active targets for SC