2.5.3. release candidate

Hi All,

I've started the build for the 2.5.3.1 release candidate, it should be uploaded in a few hours. Please test thoroughly. Other than a few critical fixes the wxWidgets portion of this build is identical to the official wxWidgets 2.5.3 release, so that would equate to CVS HEAD as of a couple weeks ago. It's possible that we could have a fairly quick turn-around on the next release once I update to CVS HEAD again and evaluate the new fixes and features that have been added since then...

I'm trying something a little different with the RC builds this time and just appending a "rcN" to the version rather than incrementing the subrelease number (4th component of the version) for each candidate. I think that this will cause a little less confusion and will also fit better with wxWidgets now that it is tracking the subrelease number too. The only downside is that I can no longer take the last RC build and call it the release and upload it to SF, but now that the build is totally automated I can more easily ensure that the final build will be the exact duplicate of the last RC, other than the version number.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi,

  • On MacOS (jaguar) this method doesn’t work

    wx.Panel.init(self, parent …

    self.Bind(wx.EVT_LEFT_UP, self.OnLeftUp)

if I replace by this, there is no problem:

self.Bind(wx.EVT_LEFT_DOWN, self.OnLeftUp)
  • In wxStaticBoxSizer, all widgets don’t get the mouse event.

I can not set the focus into a wxTextCtrl and I can not

click on a button.

  • In the demo, self.OnRightClick don’t work for the listctrl.

(wx.EVT_COMMAND_RIGHT_CLICK, wx.EVT_RIGHT_UP)

  • On the listctrl, I can’t do a simple drag.

  • There is a display problem for the notebook pages

wxNotebook.png

when I resize the window, the display is normal. The same display is on
the

demo. All the images of this pages are with an alpha channel.

  • All work fine on Windows and GTK

  • There is an unicode version for panther, and for jaguar?

Best Regards.

webmaster wrote:

  Hi,

- On MacOS (jaguar) this method doesn't work

    wx.Panel.__init__(self, parent ...
    self.Bind(wx.EVT_LEFT_UP, self.OnLeftUp)

if I replace by this, there is no problem:

    self.Bind(wx.EVT_LEFT_DOWN, self.OnLeftUp)

Please enter a bug report about this with a "wxMac specific" category and mention that it only happens on Jaguar.

- In wxStaticBoxSizer, all widgets don't get the mouse event.
I can not set the focus into a wxTextCtrl and I can not
click on a button.

The wx.StaticBox must be created before the controls that will be contained within it.

- In the demo, self.OnRightClick don't work for the listctrl.
(wx.EVT_COMMAND_RIGHT_CLICK, wx.EVT_RIGHT_UP)

Please enter a bug report about this one too, with the same criteria as above.

- On the listctrl, I can't do a simple drag.

Please explain further.

- There is a display problem for the notebook pages
notebook
when I resize the window, the display is normal. The same display is on the
demo. All the images of this pages are with an alpha channel.

Does it work better if the images have a mask instead of an alpha channel?

- There is an unicode version for panther, and for jaguar?

The platform APIs needed to implement the unicode conversions in wxWidgets were not introduced by Apple until Panther. (That is my understanding of the issue anyway.)

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

Going through the demo right now. The uninstaller, BTW, now kicks ass. :wink: It caught every remnant piece of every wxPython install I ever performed, and let me blast 'em all. =) This is very nice for OS X users, particularly because it installs into "Unix" locations. It'd be nice to have a GUI for it that would let you perform multiple uninstall operations at the same time, but as it is it is a very helpful utility. (I might even take a crack at it later, I could even just modify wxPackageManager.) In fact, I'd eventually like it to not only handle uninstall ops, but allow "on the fly" switching of the wxPython default version. (This will only work if common files are installed into the version specific wxPython dirs, though.)

As for the demo itself, there's one thing I wanted to call your attention to. When I try to run wxPopupWindow, wxPopupControl, or other unimplemented demos on Panther (10.3.5), of course it properly says the demo doesn't work on Mac, but it seems also to have loaded part of that demo's controls and data (like the script), and the unsized STC window sticks permanently on the demo. Can you (or anyone else) reproduce this? Just click on the wxPopupWindow demo then click on any other demo. I think the proper operation would probably to be to have everything load, but have the demo part do nothing.

The I've seen a couple other little things so far (wxSlider labels, grr, and wxTextCtrl invalidation after disappearing) that are annoying yet minor things. I definitely think they need to be fixed for 2.6, but may be OK for this release at least.

I'll let you know if I spot anything else major.

Thanks,

Kevin

···

On Oct 29, 2004, at 12:04 PM, Robin Dunn wrote:

Hi All,

I've started the build for the 2.5.3.1 release candidate, it should be uploaded in a few hours. Please test thoroughly. Other than a few critical fixes the wxWidgets portion of this build is identical to the official wxWidgets 2.5.3 release, so that would equate to CVS HEAD as of a couple weeks ago. It's possible that we could have a fairly quick turn-around on the next release once I update to CVS HEAD again and evaluate the new fixes and features that have been added since then...

I'm trying something a little different with the RC builds this time and just appending a "rcN" to the version rather than incrementing the subrelease number (4th component of the version) for each candidate. I think that this will cause a little less confusion and will also fit better with wxWidgets now that it is tracking the subrelease number too. The only downside is that I can no longer take the last RC build and call it the release and upload it to SF, but now that the build is totally automated I can more easily ensure that the final build will be the exact duplicate of the last RC, other than the version number.

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org

Kevin Ollivier wrote:

Going through the demo right now. The uninstaller, BTW, now kicks
ass. :wink: It caught every remnant piece of every wxPython install I
ever performed, and let me blast 'em all. =) This is very nice for OS
X users, particularly because it installs into "Unix" locations.

There may still be some holes in it, but I think that all the typical cases are covered.

In
fact, I'd eventually like it to not only handle uninstall ops, but
allow "on the fly" switching of the wxPython default version. (This
will only work if common files are installed into the version
specific wxPython dirs, though.)

I've thought about having a simple utility app that does this, but
havn't done any work on it yet.

As for the demo itself, there's one thing I wanted to call your attention to. When I try to run wxPopupWindow, wxPopupControl, or
other unimplemented demos on Panther (10.3.5), of course it properly
says the demo doesn't work on Mac, but it seems also to have loaded
part of that demo's controls and data (like the script), and the
unsized STC window sticks permanently on the demo. Can you (or anyone
else) reproduce this? Just click on the wxPopupWindow demo then click
on any other demo. I think the proper operation would probably to be
to have everything load, but have the demo part do nothing.

Yep, I know exactly what you are talking about. I already took care of
the problem for other samples in the demo that are nothing but dialogs,
but forgot about the ones that are prevented from running normally on
OSX. I'll do it on Monday.

The I've seen a couple other little things so far (wxSlider labels,
grr, and wxTextCtrl invalidation after disappearing) that are
annoying yet minor things. I definitely think they need to be fixed
for 2.6, but may be OK for this release at least.

I'll let you know if I spot anything else major.

Thanks.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!