From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2009-11-10 14:09:08
|
On 2/11/09 19:48, John Henry wrote: > I can now be more specific about the layoutEditor error in handling the PDFWindow & FlashWindow wrappers. layoutEditor actually creates the components fine (in the same manner as htmlWindow) but when it saves the file, it always ended up with a size of (-1,-1). Of course that won't work properly. > > What do I need to do to fix this? Hmmm...this sounds familiar. I came across a similar problem with the built-in components on OSX after a particular version of wxPython came out, back in 2008, and although it won't be the same issue as you're getting it might pinpoint the code you need to modify. Take a look at the mailing list archive around October 08. The code for the layout editor will be making calls to GetBestSize() before it writes the resource file, unless you add PDFWindow to the list of excluded components. If GetBestSize returns a width and height equal to the current dimensions (which it did...and might still do...on OSX), it substitutes (-1,-1). Not sure why, and in some of the editors Kevin has added a comment querying the need to do this. -- XXXXXXXXXXX |