c2c-oerpscenario team mailing list archive

[Martin Collins <704191@xxxxxxxxxxxxxxxxxx>]

OK, I've updated the client to 1789 (I'm still on server revno 3199).
I've tried logging out, restarting the client and restarting the server.
I've tried en_US and en_GB for language (these should have different default date formats) and I've tried setting the date format to %d-%m-%Y, %Y-%m-%d and %x. Nothing has had any effect - I'm stuck with %m/%d/%Y which is only used in the US AFAIK.

I'm getting a lot of these though:

Traceback (most recent call last):
  File "/usr/lib/openerp/client/bin/widget/view/tree_gtk/parser.py", line 283, in setter
    text = self.get_textual_value(model)
  File "/usr/lib/openerp/client/bin/widget/view/tree_gtk/parser.py", line 355, in get_textual_value
    converted_val = user_locale_format.format('%d', val)
  File "/usr/lib/openerp/client/bin/tools/user_locale_format.py", line 196, in format
    formatted = group(formatted, monetary=monetary, grouping=lang_grouping, thousands_sep=thousands_sep)[0]
  File "/usr/lib/openerp/client/bin/tools/user_locale_format.py", line 124, in group
    grouping = eval(grouping)
TypeError: eval() arg 1 must be a string or code object

-- 
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/704191

Title:
  [6.0rc2] Record Modified dialog raised without modification.

Status in OpenERP GTK Client:
  Invalid

Bug description:
  Similar to https://bugs.launchpad.net/openobject-client/+bug/703712
  but different I think.

  I had some datetime fields set by datetime.datetime.now().isoformat(' '). These would cause the 'This record has been modified do you want to save it?' dialog to pop up even when nothing had been changed.
  I changed isoformat() to strftime() and the problem went away.
  It seems the fractional seconds that isoformat() adds is causing a rounding error or something in the code that checks for modification. I don't need the fractions myself but I guess someone somewhere will.

  It took me far too long just to find which fields were at fault. It
  would be nice to be told which fields have changed in the dialog like
  in Koo (which no longer works with trunk). Maybe a 'show details' type
  thing.