c2c-oerpscenario team mailing list archive

["Ferdinand @ Camptocamp" <601485@xxxxxxxxxxxxxxxxxx>]

well problem described in the initial report is "solved" by

                <field name="auto_picking" position="after">
                    <field name="sale_id"/>

instead of 
                <field name="acitve" position="after">
                    <field name="sale_id"/>

nevertheless I am not sure if the rule described in #5 is the correct way to do 
Example:
* field A is only visible for "Extended"
* field B should be placed after A, but visible for all

What AMP is saying is that B is only visible for group "Extended" which IMHO is not correct. 
at least it might create unwanted side effects as it is very difficult to find the inheriting views and it shouldn't be the job of the maintainer of field A to tell the maintainer of field B that he has added an attribute "Extended" and hence B must be placed elsewhere to be displayed.

IMHO inheritance and display logic must be completely separated.

** Changed in: openobject-addons
       Status: Invalid => 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/601485

Title:
  sale/stock_view.xml - conceptual error

Status in OpenObject Addons Modules:
  New

Bug description:
  in this file sale_id is added to the view after "active" - but it never gets displayed  (V5 and V6)  (because of no field active in the view?)

if it is displayed - which is important to be able to navigate back from picking to SO - IMHO the field "Origin" can be eliminated