Solution to the "QObject::disconnect: Unexpected null parameter" warning about argos3 HOT 6 OPEN

Running ARGoS in gdb shows that the above code segfaults on line 773 of qtopengl_lua_main_window.cpp:

m_pcLuaVariableTree->setRootIndex(m_pcLuaVariableTree->model()->index(0, 0));

See backtrace.txt for further detail.

from argos3.

Also worth noting is a segfault which is produced for a similar reason as the QObject::disconnect: Unexpected null parameter warning. I am to produce this sometime when transitioning from having a light source selected and then selecting a robot (or vice versa). Attached is a backtrace that shows that this due to an oversight in the code where it is assumed that m_pcLuaVariableTree->model() is always a valid pointer. This assumption breaks when we consider some classes of entities such as those without controllers and perhaps in this case, entities which are not composable.

from argos3.

I'm able to reproduce the error with the following code, which does not include a light source: obstacle_avoidance.zip

from argos3.

Working on it now. Thanks @allsey87 and @alanmillard for your input!

from argos3.

So, I looked at the code. I made a Buzz editor based on the Lua editor, and the Buzz editor now has new features with respect to the Lua one. Along with the new features, the Buzz editor also solves all of the issues mentioned here. I guess the best option for me is to backport the Buzz editor into the Lua one, so we would get the new features as well. It'll take a day or two - done by the weekend.

from argos3.

@ilpincy sounds good. Can you make a decision on whether to accept my proposal for #40 first though? It really should take no more than 10 minutes and I did put in two weeks of work to get to that point... It would really be appreciated.

from argos3.