c2c-oerpscenario team mailing list archive

[Gustavo Adrian Marino <769542@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Working on GTK 6.0.1, if an onchange event modifies a binary field
holding an image, the screen is not modified from the returned data but
the image is read again from the server.

If you return a new image data in the result of the onchange event, the
client detects the change but instead of using the returned data as a
new image, image contents is reread from the server. This behaviour
forces you write the image data before returning the from the onchange
event, in order to ensure the screen will be refreshed.

In my case, it was no a critical problem because it was use with
osv.memory record, but it could be annoying on database records, with
can not be written til the user does not accept the modifications.

Additionally, an useless roundtrip to server is added, and thus delays
client response

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

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

Title:
  Onchange that modifies an image is not refreshed from returned value

Status in OpenERP GTK Client:
  New

Bug description:
  Working on GTK 6.0.1, if an onchange event modifies a binary field
  holding an image, the screen is not modified from the returned data
  but the image is read again from the server.

  If you return a new image data in the result of the onchange event,
  the client detects the change but instead of using the returned data
  as a new image, image contents is reread from the server. This
  behaviour forces you write the image data before returning the from
  the onchange event, in order to ensure the screen will be refreshed.

  In my case, it was no a critical problem because it was use with
  osv.memory record, but it could be annoying on database records, with
  can not be written til the user does not accept the modifications.

  Additionally, an useless roundtrip to server is added, and thus delays
  client response