> > My point is mostly that stop() does not have any meaning > > It has the meaning of things being "stopped", not moving on their own anymore.
And *how* does it correspond to the current behavior?? Currently, when we call stop() it calls stop() recursively on all children and erase anything the current widget could have put in the dom. All these operations you would have put them in a C++ destructor, a C# dispose(), etc... not in any other method. How does it prevent widgets to 'move'?? Are they moving by the way? -- https://code.launchpad.net/~openerp-dev/openerp-web/trunk-core-extraction-1-niv/+merge/94021 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openerp-web/trunk-core-extraction-1-niv. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
