Bug 284827

Summary:	Editing empty numeric metadata fields gives invalid number order
Product:	[Applications] amarok	Reporter:	Josep Cols <josep>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	josep
Priority:	NOR
Version First Reported In:	2.4.3
Target Milestone:	2.5
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Josep Cols 2011-10-23 22:09:09 UTC

Version:           2.4.3 (using KDE 4.7.1) 
OS:                Linux

This Is a 'rare' error that occurs   when I edit the details of an entry of my local collection (an individual song or a album or the entire song lists)
When I edit an empty numeric metadata field, after introduced the first number, cursor moves to **before** this number.
Example:
I whant to enter the song number 12: I press '1' and the cursor is moved before the '1' and if them press '2', the number becomes 21'.
Ona year field, if a entry '1234', this gives 2341.
.
On the other hand, if a 'cut&paste' the number, the number is well formed.
Also, if a modifies the number, all goes OK.

Reproducible: Always

Steps to Reproduce:
See Details

Actual Results:  
The number entered is invalid

Expected Results:  
When a new value is entered in a numeric metadata field, the number must remains the typed one.

OS: Linux (i686) release 2.6.38-11-generic-pae (Ubuntu 11.4)
Compiler: gcc

Comment 1 Myriam Schweingruber 2011-10-24 12:06:00 UTC

This is already fixed in the upcoming version.

*** This bug has been marked as a duplicate of bug 277279 ***