PyGTK track editor idea

[thelusiv]

When I load hockenheim I get the following backtrace. Not sure I understand it...

Code:

Program received signal SIGSEGV, Segmentation fault.

[Switching to Thread -1210124624 (LWP 16931)]

0xb66461ba in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib/libstdc++.so.6

(gdb) bt

#0  0xb66461ba in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib/libstdc++.so.6

#1  0xb5e5dc77 in OBJECTNODE::GetName (this=0xb6143b50) at include/objects.h:57

#2  0xb5e5f7d6 in boost::python::detail::invoke<boost::python::to_python_value<std::string const&>, std::string (OBJECTNODE::*)(), boost::python::arg_from_python<OBJECTNODE&> > (rc=@0xbffc80ee, f=@0x82debd4,

    tc=@0xbffc80e0) at /usr/include/boost/python/detail/invoke.hpp:88

#3  0xb5e5f8f5 in boost::python::detail::caller_arity<1u>::impl<std::string (OBJECTNODE::*)(), boost::python::default_call_policies, boost::mpl::vector2<std::string, OBJECTNODE&> >::operator() (this=0x82debd4,

    args_=0xb64fd42c) at /usr/include/boost/python/detail/caller.hpp:199

#4  0xb5e5f950 in boost::python::objects::caller_py_function_impl<boost::python::detail::caller<std::string (OBJECTNODE::*)(), boost::python::default_call_policies, boost::mpl::vector2<std::string, OBJECTNODE&> > >::operator() (this=0x82debd0, args=0xb64fd42c, kw=0x0) at /usr/include/boost/python/object/py_function.hpp:38

#5  0xb5a066d6 in boost::python::objects::function::call () from /usr/lib/libboost_python-gcc-mt-1_33_1.so.1.33.1

#6  0x082debd0 in ?? ()

#7  0xb64fd42c in ?? ()

#8  0x00000000 in ?? ()

I think you're right on the object properties being in the main window. I did a little work on the Glade setup to do this and checked it in. It still needs work however. If you take a look at it you'll see what I mean. I'm not sure if I want to get rid of the message window, but it needs to be smaller...and easier to hide.