Bug 3451 - During data entry, move cursor after some timeout
: During data entry, move cursor after some timeout
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Setup
: unspecified
: PC Windows XP
: P2 enhancement (vote)
: ---
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-26 02:43 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-05-26 02:43:30 UTC
I see this during password entry - not sure if it works like this everywhere in the setup...  Entering two adjacent characters located on the same key is made difficult by the fact that the cursor never moves to the right.   Entering the next characters on a different key is quick because the cursor automatically moves right when a new key is pressed.  But entering two or more characters on the same key requires the user to press the right-arrow first.  This can make entering long, random passwords even more tedious than it already is.
Comment 1 Richard Titmuss 2006-07-05 02:12:33 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:07 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.