Bug 3576 - Cursor doesn't move after entering punctuation char or using up/down
: Cursor doesn't move after entering punctuation char or using up/down
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Setup
: 54
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-15 14:22 UTC by Jim McAtee
Modified: 2008-12-18 11:38 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2006-06-15 14:22:33 UTC
In addressing bug 3452, a small bug has been introduced in firmware 54.  When you either enter a character under the 1 key on the remote, or you use the up/down arrows to cycle through characters, the cursor doesn't move right when you hit a new key.  If you're not expecting this new behavior, you end up overwriting the character you've just entered.

Loosely related is bug 3451, in which you're forced to hit the right-arrow to enter a second character located on the same remote key.  The cursor should always move right - if the inactivity timeout is made relatively long (say 2 or 3 seconds) then it'll still be faster and easier than having to move the cursor manually.
Comment 1 Richard Titmuss 2006-07-05 02:12:34 UTC
This bug is fixed in firmware 56. It is currently undergoing
internal testing. You will be notified again when it is made part of
a nightly release. 
Comment 2 Chris Owens 2006-09-03 12:18:32 UTC
I apologize; I've been slow in adding this notification to some of the bugs.  Please ignore it if you've already tried the new firmware.

This bug fix is now available in the nightly Slimserver release. The release is available from:

http://www.slimdevices.com/dev_nightly.html

If you prefer to wait for the next official release, you will be notified when it occurs.

You'll need to install the new version of Slimserver, and then force your Squeezebox to upgrade its firmware by holding down the 'Brightness' button on the remote control until the firmware upgrade process begins.

If you are still experiencing this problem after upgrading your affected players to the new firmware, please reopen the bug.