From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2004-08-07 22:19:18
|
On Sat, 7 Aug 2004 08:39:12 -0700, Kevin Altis wrote: >There have been some wxWidget/wxPython bugs that could account for this >problem, but neither of the ones I submitted below actually led to an >assert. > >http://sourceforge.net/tracker/? >func=detail&aid=885104&group_id=9863&atid=109863 > >http://sourceforge.net/tracker/? >func=detail&aid=909546&group_id=9863&atid=109863 > >If you want, you can wait for wxPython 2.5.2.3 to be released or try >the wxPython-dev developer preview and see if it fixes the problem. > >http://starship.python.net/crew/robind/wxPython/preview/2.5.2.3/ > >Of course, there could be a bug in PythonCard, but that sounds unlikely >given the error you reported. > >If the image can't be handled by wxWidgets, then I would like to get it >from you, but don't email it to the list. Send me an email offlist with >the size of the image and we'll figure out how to transfer it so I can >reproduce the problem. (To the moderator(s): I posted this and the following message earlier from the wrong email address and got a warning that they were on-hold - please delete the old ones). OK....cause found. The image needs to be in the same directory as the resource file. If you use the "File" browser button to select a graphic file from a different directory then the path is not recorded in the resource file, just the file name. Presumably if I wanted to use an image in a different directory I could manually type in the path. What confused me was the error message coming back from wxPython - the invalid bitmap and handler errors don't make it clear that in fact the problem is that the application can't find the file. Having said that, the OSX error dialog's first line does give you a bit of a clue :-) Not the Windows version though. Neil |