Hi everyone,
Here we have a situation.
We all have seen samples of one2many implementation in Tree View and
form view.
It's nice to implement a one2many using this structure within the
parent form view.
<field name="something" mode"form,tree">
<treeview>
<field/>
<field/>
</treeview>
</field>
The example of this development is available in the party module where
you can add information for address.
When you click on the new button, Of course the previously entered
data into these fields will be disappeared and these fields will be
set to readonly again until user click on the small icon beside the
black titlebar of this structure. (new button).
So far everything goes well, But the problem here is that you decided
to implement a child field of the child filed using above structure
within the same page.
Everything goes well but when you click on the new button,
confusingly, the previous data within this sub structure will appears
in this tree view(of course, like 2nd child objects in party and
address implementation, it is not enable until user clicks on the new
button on the black title bar,).
It shouldn't be any problem for functionality of the module, when you
click on the new button( on the black titlebar), the previous data
will be deleted and the field becomes enable and editable and empty.
Therefore the functionality is OK and the module is working well.
But from End user point of view it's not user friendly. Unfortunately
i couldn't find any pattern within the core module to make a
comparision and to check this issue.
After some try and error techniques, Now i don't have any idea on how
to implement it.
Actually it might be a simulation if i find a way to trigger an small
new button for one2many fields, Because as i said before, By clicking
on the new button previously entered data will be disappeared.
So far i couldn't find a way to trigger this button :)
As I'm still a beginner i need your advise and direction.
--
[email protected] mailing list
