Użytkownik Uwe Grauer napisał:
> You might be able to indentify which revision change is the culprit
> by going back and forth in the past revisions.
> Knowing which exact revision did this bad change would allow the Dabo
> developers to fix it more easily.
>
I think problem is in dPageFrameMixin.__onPageChanging event handler.
First, line with call:
newPageNum = evt.GetSelection()
always return current page, not the forthcoming page.
Second, line code:
self.raiseEvent(dEvents.PageChanging, oldPageNum=oldPageNum,
newPageNum=oldPageNum) seems to completly doesn't work
if oldPageNum=oldPageNum=0, because
instead of page 0 remain active, page I clicked is activated.
--
Regards
Jacek Kałucki
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]
