[wxPython-users] App.SetAppName & App.SetVendorName

[Joe Brown]

Thanks for the reply, as always! 

I'm so sorry to bother you, I discovered the issue was related to my
foobaz.

Tried once already to do the sample, but the suspected code, didn't gpf.
After reading your anticipated suggestion of creating a sample, I was
more vigilant and found the culprit. 

In wx2.6 this didn't cause an issue.  Although I'm pretty sure it was
never a good idea to write a sizer like this:

        self.panel = wx.Panel(self, -1)
        self.Sizer = wx.BoxSizer(wx.VERTICAL)
        self.Sizer.Add(self.panel, 1, wx.EXPAND)
        self.panel.SetSizer(self.Sizer)

I can't quite configure how adjusting the config avoided gpf on close,
perhaps because I store the frame's size/ismaximized settings...  But I
suppose it's a moot point.  

I was hoping the issue I was stubbing my toe on, might be the cause of
another issue, but I don't see that a possibility now. 

Joseph

On Wed, 2007-01-31 at 16:49 -0800, Robin Dunn wrote:
> Joe Brown wrote:
> > Thought I'd try a version of wxPython latter than 2.6.
> > 
> > My Application keeps gpf's on exit...  This makes no sense to me.
> > 
> > My first suspect was the App class, so I started inspecting my OnInit
> > and discovered that if I comment out the piece where it sets both
> > AppName & VendorName...  I get to run it once w/out crash then the next
> > execution, it crashes (gpf) on exit.
> > 
> > I've tried commenting out the config.read/writes and that doesn't appear
> > to have any affect.
> > 
> > I haven't been able to isolate the cause any further.
> > 
> > XP, Python 2.4 & wxPython 2.8 I think this behavior also existed in 2.7
> > 
> > Commenting app/vendor settings works for one execution of my program,
> > but then subsequent executions also gpf.
> 
> So, if it is related to the config, this leads me to believe that it has 
> to do with using values that are read from the config instead of 
> whatever you use for defaults, (because changing the app/vendor names 
> would essentially mean you are starting without a config the time that 
> works.)  If that doesn't help you track it down further then try making 
> a sample app that does nothing but use a config object similar to how 
> you are doing it in your app, and see if that duplicates the problem.
> 
> http://wiki.wxpython.org/index.cgi/MakingSampleApps
>