Segfault on basic startup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Follow the instructions in the Installation Guide
2.
3.

What is the expected output? What do you see instead?

I expected the designer to start.

I got a segfault:

momerath:gui2py-0.9.3 mgregory$ python
Python 2.7.3 (default, Apr 19 2012, 11:51:19) 
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx
>>> wx.version()
'2.9.4.0 osx-cocoa (classic)'
>>> exit()
momerath:gui2py-0.9.3 mgregory$ python -c "import gui; print gui.__version__"
0.9.3
momerath:gui2py-0.9.3 mgregory$ python -m gui.tools.designer sample.pyw
Segmentation fault: 11
momerath:gui2py-0.9.3 mgregory$ 

What version of the product are you using? On what operating system?

see above (osx 10.8.5)

Original issue reported on code.google.com by martin.g...@astc-design.com on 28 Sep 2013 at 12:32

[GoogleCodeExporter]

I get a segfault when running sample.pyw. I hadn't noticed it in my own program 
until I tried adding a menubar. The first few frames of the backtrace are:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libwx_osx_cocoau-2.9.4.0.0.dylib    0x0000000110e1662a 
wxWindow::SetDropTarget(wxDropTarget*) + 58
1   _core_.so                       0x00000001109f533e 
_wrap_Window_SetDropTarget + 222
2   org.python.python               0x000000010fffaf72 PyEval_EvalFrameEx + 3557
3   org.python.python               0x000000010fffa147 PyEval_EvalCodeEx + 1934
4   org.python.python               0x00000001100008df 0x10ffe3000 + 121055

This is with '2.9.4.0 osx-cocoa (classic)' and momerath:gui2py-0.9.3 on Mac OS 
X 10.8.5.

Original comment by crows...@gmail.com on 11 Oct 2013 at 12:20

[GoogleCodeExporter]

The problem was in component.py: it was passing None to 
self.wx_obj.SetDropTarget. Maybe a bug in wx? I'm using version 2.9.4, which 
isn't the latest. I patched component.py to check if dt was None before calling 
SetDropTarget and menus now work. 

Original comment by crows...@gmail.com on 17 Oct 2013 at 1:37