c2c-oerpscenario team mailing list archive

[Nicolas DS <455547@xxxxxxxxxxxxxxxxxx>]

Hi Anup,
with the patches I provided everything works as expected in all conditions.
Even in the case you describe  (add a field between 2 previously created)
I removed in the patches the code no more usefull. (saving the next item)

It works like this:
Original nodes :
+ A
+ B
+ C
Nodes to add after B:
+D
+E

With the patches:

1. Deal with D:
node = B
child = D
node.addnext(child)
node = child = D
1. Result:
+ A
+ B
+ D
+ C

2. Deal with E:
node = D (thank's to the "node = child")
child = E
node.addnext(child)
node = child
2. Result:
+ A
+ B
+ D
+ E
+ C

As expected...

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

Title:
  Using position="after" in inherited view adds the fields in reverse order

Status in OpenObject Server:
  In Progress
Status in OpenObject Server 5.0 series:
  In Progress
Status in OpenObject Server trunk series:
  In Progress

Bug description:
  Applies to 5.0.6

For example, if I use the following 'arch' XML in an inherited view:

            <field name="arch" type="xml">
                <field name="my_field" position="after">
                    <field name="field1" />
                    <field name="field2" />
                    <field name="field3" />
                    <field name="field4" />
                </field>
            </field>

The resulting screen will display the fields in the following order:

my_field
field4
field3
field2
field1

My guess is that the server is calling the 'insert after' xml method for each sub-tag in order.

The fix will be to call the 'insert after' xml method for each of the sub-tags in reverse order, so that field1 is inserted last, so it appears directly after my_field

I will use the position="replace" method as a workaround for now.