Instead of a big button, the button appears at normal height but duplicated repeatedly for the total height of the button size. This is new since 2.5.1.1. It looks like other controls are okay, but I haven't checked them all.
This brings up another issue... Stefan just today committed all those changes that he and I have been working on, and the changes are pretty significant, so I'm not sure it makes much sense to debug the old code at this point. For the most part, the new code works well, but there are background drawing issues that need to be worked out and a few control specific issues, mostly trivial things like spacing. There are also a couple issues with wxButton that I haven't gotten to the bottom of as well. (One is similar to what you've reported, only the button does not repeat - it just stays the same height as the default.)
On the upside, wxListBoxes *definitely* look better than before, as do a number of other controls. I'm not seeing any of those weird glitches like thick shadows, etc. Anti-aliasing definitely seems to look nicer now too.
Should we consider holding off on the wxPythonOSX release for a bit, and putting out a preview release with the new Mac implementation in the next week or two once the major bugs have been ironed out? I think if we can get the background problems and the wxButton issues resolved, and barring I find anything else major (I've run many of the C++ samples so far) then I think it should be ready for a preview release at least.
Thanks,
Kevin
···
On Mar 27, 2004, at 2:12 PM, Kevin Altis wrote:
Instead of a big button, the button appears at normal height but duplicated repeatedly for the total height of the button size. This is new since 2.5.1.1. It looks like other controls are okay, but I haven't checked them all.
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
Should we consider holding off on the wxPythonOSX release for a bit, and putting out a preview release with the new Mac implementation in the next week or two once the major bugs have been ironed out? I think if we can get the background problems and the wxButton issues resolved, and barring I find anything else major (I've run many of the C++ samples so far) then I think it should be ready for a preview release at least.
I didn't want to hold up the release waiting for the dust to settle on wxMac, so I tagged CVS before all those changes were checked in. Once the dust settles and the kinks are worked out then we can do another release.
Kevin A. has found a problem with threaded apps so this release make not make it to general release after all, so we may get the new mac stuff in the release anyway, if I need to update from CVS to fix this problem...
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
We haven't made a request for brave souls to join the testing ranks in quite a while. Could you make such a request for folks that want to do real testing on any or all platforms to join wxPython-dev to help make sure 2.5.x is a great release? I would do it, but you have more clout
ka
···
On Mar 27, 2004, at 6:43 PM, Robin Dunn wrote:
Kevin Ollivier wrote:
Should we consider holding off on the wxPythonOSX release for a bit, and putting out a preview release with the new Mac implementation in the next week or two once the major bugs have been ironed out? I think if we can get the background problems and the wxButton issues resolved, and barring I find anything else major (I've run many of the C++ samples so far) then I think it should be ready for a preview release at least.
I didn't want to hold up the release waiting for the dust to settle on wxMac, so I tagged CVS before all those changes were checked in. Once the dust settles and the kinks are worked out then we can do another release.
Kevin A. has found a problem with threaded apps so this release make not make it to general release after all, so we may get the new mac stuff in the release anyway, if I need to update from CVS to fix this problem...