Użytkownik Dabo Trac napisał: > #1200: Incorrect event handling in ui.dPageFrameMixin.__onPageChanging > ---------------------+------------------------------------------------------ > > Reporter: JacekK | Owner: somebody Type: > defect | Status: new Priority: major | > Milestone: 0.9 Component: ui | Version: > 0.9.1 Resolution: | Keywords: pageframe events > ---------------------+------------------------------------------------------ > > Comment (by ed): > > I'm not sure what the issue is here. If I'm on page 2 and then run a > query > that results in no records, and then try to click on any other page, I > should be taken to page 0. > > If there are no records and I'm on page 0, clicking on the other page > tabs > does nothing. > >
But in my wizard generated example, there is no such behavior. I repeat, if there are no records and I'm on page 0 and I click on page 1, page 1 is activated. Then if I click page 2, page 0 is activated, and next if I click page 2 again, page 2 is activated. Additionally, "newPageNum" variable in dPageFrameMixin.__onPageChanging always has the same vale as "oldPageNum" when event is user generated, except situation when is generated with raiseEvent method in code (-1 at init). So how can I predict further page number in such situation? My environement is: - Windows XP SP3 - Python 2.5.2 - wxPython 2.8.9.1 - dabo 0.9.1 SVN 5068 -- 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]
