Użytkownik Paul McNett napisał: > dabo Commit > Revision 6150 > Date: 2010-10-24 10:11:34 -0700 (Sun, 24 Oct 2010) > Author: Paul > Trac: http://trac.dabodev.com/changeset/6150 > > Changed: > U trunk/dabo/ui/uiwx/dPageFrameMixin.py > > Log: > Fixes the update() problem with pageframes on Win and Mac, introduced in > r6050. > > > Diff: > Modified: trunk/dabo/ui/uiwx/dPageFrameMixin.py > =================================================================== > --- trunk/dabo/ui/uiwx/dPageFrameMixin.py 2010-10-24 15:30:02 UTC (rev > 6149) > +++ trunk/dabo/ui/uiwx/dPageFrameMixin.py 2010-10-24 17:11:34 UTC (rev > 6150) > @@ -86,7 +86,12 @@ > return > > if newPageNum>= 0 and self.PageCount> newPageNum: > - dabo.ui.callAfter(self.Pages[newPageNum].raiseEvent, > dEvents.PageEnter) > + newPage = self.Pages[newPageNum] > + ## On Mac and Win, wx.GetShown() returns False for > inactive pages, > + ## so update() would have been ignored for this > newly-coming-active > + ## page. Therefore, call it unconditionally now: > + newPage.update() > + dabo.ui.callAfter(newPage.raiseEvent, dEvents.PageEnter) > dabo.ui.callAfter(self.raiseEvent, dEvents.PageChanged, > oldPageNum=oldPageNum, > newPageNum=newPageNum) >
Hi. I can't understand what update() has to do with page change. Since this method updates current controls values from data source, and if I didn't change my data, I don't want my controls to be redundantly updated. BTW, 'update' name is confusing with wx 'Update', but its purpose is differ. -- Regards Jacek Kałucki _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
