On 7/10/11 6:12 AM, Jacek Kałucki wrote: > I was always intrigued, why while wxPython demos are perfectly still, > Dabo form flickers like hell on Windows platform. > Then I figured out that source of problem is intensive usage of the refresh > method. > In my tests I commented out all refresh calls in dForm navigation methods > (next, etc.). > I also disabled all conditional, platform dependent refreshes. > As far I can't see negatives and the positives are especially visible > on controls with background, like dBitmapButton or dImage. > I tested my changes on Ubuntu GTK 2.24 wx 2.8.11 and Windows7 wx 2.8.12. > Taking above, I vote for removing redundant refreshes or at last, > adding method to verify if refresh is needed, e.g. > dPemMixin._checkPlatformRefresh, > where we can force refreshes for Windows platform and wx older than 2.8.
+1 on doing systematic testing on all platforms for removing redundant refresh calls. I think wxPython has gotten better over the years, removing the need for refreshes in places where it used to be required. Paul _______________________________________________ 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]
