← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 680597] Re: KP_Decimal should be the locale decimal separator in spinbutton entries

 

*** This bug is a duplicate of bug 697625 ***
    https://bugs.launchpad.net/bugs/697625

** This bug is no longer a duplicate of bug 519227
   Not possible to input for floating field widget with comma and dot
** This bug has been marked a duplicate of bug 697625
   Clients should respect locale parameters defined in OpenERP locales (thousands separator, etc.)
 * You can subscribe to bug 697625 by following this link: https://bugs.launchpad.net/openobject-client/+bug/697625/+subscribe

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/680597

Title:
  KP_Decimal should be the locale decimal separator in spinbutton
  entries

Status in OpenERP GTK Client:
  Triaged

Bug description:
  When entering a number in the spinbutton entry (the one assigned for
  floats), the KP_Decimal button is always a dot.

  In applications like OpenOffice or GNUCash, when users use the keypad
  in a locale where the decimal separator is a comma, the KP_Decimal
  button produces a comma.  However, in normal GTK applications this is
  not the case.

  This is related to a decision of the people of GTK/X, to follow whatever is printed on the keyboard instead of what the user actually expects to happen:
  http://bugs.xfree86.org/show_bug.cgi?id=534

  I consider that entering numbers in a quick fashion and respecting the
  user's spectation takes priority over respecting whatever the
  manufacturer of the keyboard decided to print on it.  In some cases,
  like in the case of Spanish keyboards, different manufacturers print
  different stuff on the KP_Decimal key.

  I have made a patch for the 5.0.14 version of openerp-cient, that
  modifies the spinbutton class in order to get the expected behaviour.

  As soon as possible I'll be attaching a similar patch for the 6.X
  versions (I trust that it'll be similar enough, since the change is
  quite small).





References