sofa-framework / sofaqtquick Goto Github PK

The rational behind is that the list model is not supposed to be for tree like structure and visualization aspect are implemented in the model itself instead of using proxies as in:
http://doc.qt.io/archives/qt-4.8/qsortfilterproxymodel.html#details

The SofaSceneItemModel is crashing when trying to add node to the root.
(this also happens in the 3D view when picking objects)

While the root node is a perfectly valid node in the scenegraph it is not reported as is in when
clicking on the scenegraph view.

eg:
sofaScene.selectedComponent is null

This is a follow-up task after STC5.

During STC5 it was agreed that having a way to visualize the data graph would be nice.

I think the interested people were:
@marques-bruno, @hugtalbot, @sescaida

Do you have time to work on that in the next weeks so we can have a preview before holiday ?

Choose 'selector' interaction
Then select some stuff in the scene, this work.
The collapse the node in the scene graph
Then select does not work...try multiple time...it finally crahs

Further to discussions with the company Anatoscope, it has been proposed to share the administration with the SOFA consortium in order to support the maintenance and improvement of this work. The original repository can be found here.

Our purpose with SofaQtQuick is to propose by the end of 2018 (at the latest) a new GUI for SOFA based on this work.

This issue aims at describing the roadmap of the next months (2018):

• from January 2018, push in SOFA the cmake feature "external project" allowing for pulling automatically the SofaQtQuick repository within the applications/project folder, if the experimental option is activated in SOFA
• separate the code between the library itself (SofaQtQuick) and the executable (runSofa2)
• implement tests and improve existing codes
• export the libraries depending on optional plugins (ex: ImageQtQuickWidget)
• when stable (target 18.06 release), merge finally into SOFA

Advantages of the approach: easy to use, easy to contribute, visible, experimental period, possibility to benefit from the improvements made on the code until merge.

Any feedback is obviously welcome.
Interested to contribute, contact us, we are waiting for you!

The crash happens on light.cpp because of invalid initialization process.
I'm investigating this part.

@marques-bruno do you have to work on this one or should I work on that ?