wxPy2.5.2.3p.20040723 on win98

wxPython Dev
1

Hi,

win98, Py234, wxPy2.5.2.3p.20040723

1) As P. Damoc noticed, if the real release number is 2.5.2.3, the files, changes.html
and changes.txt, should be updated.

2) A quick look at the demo
Seems to be ok on my platform. The only black point I noticed lies in the
TreeListCtrl demo. The horizontal and vertical lines joining the items (icons) are not
refreshed correctly. These lines, or some segments, are not always redrawn.

3) Test with some of my apps.
Ok.
I hope, I can remove the "import fixdc" line soon.

4) About the SplitterWindow (remember the discussion on the users-list), the code
proposed by P. Damoc is now working; understand the sash is moving correctly.
About the desappearing sash, I wonder if this is a real bug or a "design" issue. It appeared
that the SashPosition is sometimes negative. I hope to have the time to make more tests.

5) I also had a look at the new doc. Nice. When browsing, I fall on the wx.pySimpleApp
page. In the given example:

app = wx.PySimpleApp()
frame = wx.Frame(None, title='Hello World')
frame.Show()
app.MainLoop()

should not the second line be
frame = wx.Frame(None, -1, title='Hello World') ?

Jean-Michel Fauth, Switzerland

2

Jean-Michel Fauth wrote:

Hi,

win98, Py234, wxPy2.5.2.3p.20040723

1) As P. Damoc noticed, if the real release number is 2.5.2.3, the files, changes.html
and changes.txt, should be updated.

Yep.

5) I also had a look at the new doc. Nice. When browsing, I fall on the wx.pySimpleApp
page. In the given example:

app = wx.PySimpleApp()
frame = wx.Frame(None, title='Hello World')
frame.Show()
app.MainLoop()

should not the second line be
frame = wx.Frame(None, -1, title='Hello World') ?

No. From CHANGES.txt:

"""
Added more default args as needed to allow most window types to be
constructed with only the parent window arg. In some cases other args
may be required for normal operation, but they can usually be set
after construction.
"""

Once more of the docstrings are added then the NewDocs for wx.Frame and the others will show the new defaults. But you can also see it in the default docstring:

> pydoc wx.Frame.__init__

Help on method __init__ in wx.Frame:

wx.Frame.__init__ = __init__(self, *args, **kwargs) unbound wx._windows.Frame method
     __init__(self, Window parent, int id=-1, String title=EmptyString,
         Point pos=DefaultPosition, Size size=DefaultSize,
         long style=DEFAULT_FRAME_STYLE, String name=FrameNameStr) -> Frame

···

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

3

Oh YEAH! :slight_smile: long live the defaults :slight_smile:
Lately I've seen a lot of nice surprises :slight_smile: Nice too see wxpython moving from wxwidgets closer to "batteries included" :slight_smile:

I have a question about overweight/performance... would lines like the next hurt performance/ memory consumption of wxpython?

self.InstallMenuHandlers =lambda list: map(lambda (id, handler): self.Bind(wx.EVT_MENU, handler, id=id), list)

if this being in the code of wx.Frame hurts how about putting it in wx.swissknife ? :o)

···

On Sat, 24 Jul 2004 16:59:53 -0700, Robin Dunn <robin@alldunn.com> wrote:

wx.Frame.__init__ = __init__(self, *args, **kwargs) unbound wx._windows.Frame method
     __init__(self, Window parent, int id=-1, String title=EmptyString,
         Point pos=DefaultPosition, Size size=DefaultSize,
         long style=DEFAULT_FRAME_STYLE, String name=FrameNameStr) ->

--
Peter Damoc
Hacker Wannabe
http://www.sigmacore.net/