Thu, 07 Jan 2010 16:52:32 +0100 update copyright: welcome 2010 stable
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Thu, 07 Jan 2010 16:52:32 +0100] rev 4212
update copyright: welcome 2010
Thu, 07 Jan 2010 08:02:52 +0100 [views] backport progressbar template from shingouz
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Thu, 07 Jan 2010 08:02:52 +0100] rev 4211
[views] backport progressbar template from shingouz
Tue, 05 Jan 2010 22:11:37 +0100 [forms] fix multiple edit bug introduced by changeset cebdf8ee5ad7 stable
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Tue, 05 Jan 2010 22:11:37 +0100] rev 4210
[forms] fix multiple edit bug introduced by changeset cebdf8ee5ad7 Changeset cebdf8ee5ad7 assumed that edited entity was either explicitly passed to the form or found in first row / first col of the resultset because of the one_line_rset() selector. But one_line_rset() is actually trickier : the selector returns 1 if the resultset has more than one row **if** an explicit row is specified during selection process. This is exactly what is done in the 'muledit' form : for row in xrange(len(self.rset)): form = self.vreg['forms'].select('edition', self.req, rset=self.rset, row=row, #... This changeset thus takes row in consideration to find edited entity if 'row' was explcitly specified.
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip