20120519 test build uploaded

1 view
Skip to first unread message

R'bot

unread,
May 19, 2012, 3:44:43 PM5/19/12
to wxPyth...@googlegroups.com
Hi,

A new test build of wxPython has been uploaded.

Version: 2.9.4.0.b20120519
URL: http://wxPython.kosoftworks.com/preview/20120519
Changes: http://wxPython.kosoftworks.com/preview/20120519/CHANGES.html

Have fun!
R'bot

Werner

unread,
May 20, 2012, 6:01:05 AM5/20/12
to wxpyth...@googlegroups.com
Hi Robin,

A couple more:

- InfoBar the AGW one seems only to be a copy of the wx one, i.e.
InfoBar is used as wx.InfoBar and no import from AGW.
- XLSGridDemo - when clicking start I get "Error: the file Example_1.xls
is not in the data directory"

Werner

Werner

unread,
May 20, 2012, 5:45:56 AM5/20/12
to wxpyth...@googlegroups.com
Hi,

Issues I found in the demo:

- Preview in the print framework shows this error:

Traceback (most recent call last):
  File "PrintFramework.py", line 64, in OnPrintPage
    (w, h) = dc.GetSizeTuple()
AttributeError: 'PySwigObject' object has no attribute 'GetSizeTuple'

Major change in my own app:
2.9.3:


2.9.4:


Layout is not the same and validator do no longer update values into controls.

All this by just changing:
wxversion.select('2.9.3')
to:
wxversion.select('2.9.4')

Any hints on what has changed in 2.9.4 which causes such changes?

BTW, what is the status of the StaticBox? Should controls be siblings, should one still use StaticBoxSizer?

Will work through the demo and also try to debug where things go wrong with my app.

Werner

Werner

unread,
May 20, 2012, 9:29:46 AM5/20/12
to wxpyth...@googlegroups.com
Hi Robin,

On 20/05/2012 11:45, Werner wrote:

...

Layout is not the same and validator do no longer update values into controls.
The validator problem is due to a change in wx.lib.sized_controls.

self.SetExtraStyle(wx.WS_EX_VALIDATE_RECURSIVELY)

has been removed everywhere except for the SizedDialog?!

Will it be left like that?

Werner

Werner

unread,
May 20, 2012, 9:48:03 AM5/20/12
to wxpyth...@googlegroups.com
Hi Robin,

On 20/05/2012 11:45, Werner wrote:
...
> Layout is not the same and validator do no longer update values into
> controls.
The Layout issue is due to masked edit, some time ago I suggested a
change to how it calculates the control size, obviously this change
didn't make it.

Any chance the change (see attached email with patch) could be
considered for inclusion in 2.9.4?

Werner
maskededitbettersizing.patch

Werner

unread,
May 22, 2012, 5:57:00 AM5/22/12
to wxpyth...@googlegroups.com
Hi,

When trying the "ShortcutEditor" demo I get a no such file
("...../default_help_text.html").

Werner

Robin Dunn

unread,
May 28, 2012, 6:01:24 PM5/28/12
to wxpyth...@googlegroups.com
On 5/20/12 2:45 AM, Werner wrote:
> Hi,
>
> Issues I found in the demo:
>
> - Preview in the print framework shows this error:
>
> Traceback (most recent call last):
> File "PrintFramework.py", line 64, in OnPrintPage
> (w, h) = dc.GetSizeTuple()
> AttributeError: 'PySwigObject' object has no attribute 'GetSizeTuple'
>

Fixed.


> Major change in my own app:
> 2.9.3:
>
>
> 2.9.4:
>
>
> Layout is not the same and validator do no longer update values into
> controls.
>
> All this by just changing:
> wxversion.select('2.9.3')
> to:
> wxversion.select('2.9.4')
>
> Any hints on what has changed in 2.9.4 which causes such changes?

I'm not sure. I don't recall anything specific.


>
> BTW, what is the status of the StaticBox? Should controls be siblings,
> should one still use StaticBoxSizer?

Either way is supposed to work. On wxMSW some adjustments need to be
made to handle the spacing correctly when the widgets are children of
the StaticBox (that does already work on the other platforms.) I
volunteered to do it but haven't gotten to it yet. I'll try to do it
before the next preview build.


--
Robin Dunn
Software Craftsman
http://wxPython.org

Robin Dunn

unread,
May 28, 2012, 6:02:03 PM5/28/12
to wxpyth...@googlegroups.com
On 5/20/12 3:01 AM, Werner wrote:
> Hi Robin,
>
> A couple more:
>
> - InfoBar the AGW one seems only to be a copy of the wx one, i.e.
> InfoBar is used as wx.InfoBar and no import from AGW.

The demo files are different, but it looks like the demo itself is
simply not loading the one from AGW when it finds a matching name in the
mail demo folder. A simple rename should take care of it.

> - XLSGridDemo - when clicking start I get "Error: the file Example_1.xls
> is not in the data directory"

There is a line in the installer that should add this file to the list.
Can you verify that it is or is not there or perhaps put in the wrong
place?

Robin Dunn

unread,
May 28, 2012, 6:02:24 PM5/28/12
to wxpyth...@googlegroups.com
Are you sure that wasn't a change you made locally? I don't see it
being removed in any of the recent updates to that file. See:

http://trac.wxwidgets.org/log/wxPython/trunk/wx/lib/sized_controls.py

Robin Dunn

unread,
May 28, 2012, 6:02:30 PM5/28/12
to wxpyth...@googlegroups.com
Done.

Werner

unread,
May 29, 2012, 2:04:50 AM5/29/12
to wxpyth...@googlegroups.com
Hi Robin,
I just deleted my demo and reinstalled it.

The file is in:
C:\Python27\Doc\wxPython2.9 Docs and Demos\demo\agw\data

but I still get the error when I click on "Start", will try and dig a
bit more later today and see if I can provide more information.

Werner

Werner

unread,
May 29, 2012, 2:09:43 AM5/29/12
to wxpyth...@googlegroups.com
Hi Robin,

On 29/05/2012 00:01, Robin Dunn wrote:

...
>> 2.9.3:
>>
>>
>> 2.9.4:
>>
>>
>> Layout is not the same and validator do no longer update values into
>> controls.
>>
>> All this by just changing:
>> wxversion.select('2.9.3')
>> to:
>> wxversion.select('2.9.4')
>>
>> Any hints on what has changed in 2.9.4 which causes such changes?
> Major change in my own app:
>
> I'm not sure. I don't recall anything specific.
One was due to the SizedControls (will just sub-class to add the
"self.SetExtraStyle(wx.WS_EX_VALIDATE_RECURSIVELY) ", must have thought
to provide a patch for this and never did- sorry for having you to chase
this) and the other the masked change which you applied according to the
other post.
>
>
>>
>> BTW, what is the status of the StaticBox? Should controls be siblings,
>> should one still use StaticBoxSizer?
>
> Either way is supposed to work. On wxMSW some adjustments need to be
> made to handle the spacing correctly when the widgets are children of
> the StaticBox (that does already work on the other platforms.) I
> volunteered to do it but haven't gotten to it yet. I'll try to do it
> before the next preview build.
That would be great.

Thanks
Werner
Reply all
Reply to author
Forward
0 new messages