I am having a serious problem with adding in FlashWindow to my
project. When using it, the size seems to be limited to much smaller
then I am specifying. If I try and call it using 960, 600 the window
that it loads is limited severely.
I have uploaded a test project that shows this issue here.
So you end up with 600 for the x arg and nothing for the y arg so it defaults to 300.
···
On 5/29/11 3:10 PM, adam wrote:
I am having a serious problem with adding in FlashWindow to my
project. When using it, the size seems to be limited to much smaller
then I am specifying. If I try and call it using 960, 600 the window
that it loads is limited severely.
I have uploaded a test project that shows this issue here.
I actually tested by changing the set size line to
Flash.SetSize(960,600)
But it still makes it the same size.
···
On May 30, 4:00 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 5/29/11 3:10 PM, adam wrote:
> I am having a serious problem with adding in FlashWindow to my
> project. When using it, the size seems to be limited to much smaller
> then I am specifying. If I try and call it using 960, 600 the window
> that it loads is limited severely.
> I have uploaded a test project that shows this issue here.
What version of wxPython are you using? For me it appears to be setting that size as the flash window's minsize at the time of the first layout (since it has no children or sizer of its own.) But I'm not sure when that feature was added. Try changing the SetSize to SetMinSize, or just pass the size to the FlashWindow constructor in the previoius line. In the sizer code the minsize (if set) takes precedence over the the current size and best size.
You may also want to use the WIT to help you examine the layout and related properties of the live application. It can really help to gain an understanding of how things work or why things are misbehaving. http://wiki.wxpython.org/Widget_Inspection_Tool
···
On 5/30/11 2:11 PM, adam wrote:
I actually tested by changing the set size line to
Calling the size change in the constructor worked. Thank you
···
On May 30, 6:13 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 5/30/11 2:11 PM, adam wrote:
> I actually tested by changing the set size line to
> Flash.SetSize(960,600)
> But it still makes it the same size.
What version of wxPython are you using? For me it appears to be setting
that size as the flash window's minsize at the time of the first layout
(since it has no children or sizer of its own.) But I'm not sure when
that feature was added. Try changing the SetSize to SetMinSize, or just
pass the size to the FlashWindow constructor in the previoius line. In
the sizer code the minsize (if set) takes precedence over the the
current size and best size.
You may also want to use the WIT to help you examine the layout and
related properties of the live application. It can really help to gain
an understanding of how things work or why things are misbehaving.http://wiki.wxpython.org/Widget_Inspection_Tool
--
Robin Dunn
Software Craftsmanhttp://wxPython.org