c2c-oerpscenario team mailing list archive

["Xavier ALT \(Thamini\)" <666631@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi,

Spinint widget doesn't handle the case where the fields.integer() value
received from the server is a instance of "long".

Steps to reproduce the problem:
==========================
1. Create a PostgreSQL view and declare a fields.interger() for the corresponding column.
2. Create a tree and a form view for this object (displaying the integer field)
3. Open the view
3.1: Tree view no problem, the value is display correctly
3.2: Switching to Form view, the field content now is "0" (zero).
3.3: When switching back to tree view, the client ask for saving modification (actually nothing was modified).

The server send the value from the PostgreSQL view, which is "long".
When displaying this value onto the "spinint" form widget, the "long"
case is not handle and the value is reset to "0", that let the client
think the record was modified.

See patch attached which fix the problem.
Thanks!

** Affects: openobject-client
     Importance: Undecided
         Status: New

-- 
[5.0] gtk client doesn't handle long int into form view (spinint widget)
https://bugs.launchpad.net/bugs/666631
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject GTK Client: New

Bug description:
Hi,

Spinint widget doesn't handle the case where the fields.integer() value received from the server is a instance of "long".

Steps to reproduce the problem:
==========================
1. Create a PostgreSQL view and declare a fields.interger() for the corresponding column.
2. Create a tree and a form view for this object (displaying the integer field)
3. Open the view
3.1: Tree view no problem, the value is display correctly
3.2: Switching to Form view, the field content now is "0" (zero).
3.3: When switching back to tree view, the client ask for saving modification (actually nothing was modified).

The server send the value from the PostgreSQL view, which is "long". When displaying this value onto the "spinint" form widget, the "long" case is not handle and the value is reset to "0", that let the client think the record was modified.

See patch attached which fix the problem.
Thanks!