Evgenii Startcev

It seems it is indeed related to https://github.com/f3d-app/f3d/pull/2151. Though fully correct implementation is still under question. I tried ShallowCopy, with it I noticed skeleton starts being always with spherical joints....

It should be related to ability to get argument completion help for console. I could work on it once I finish the current stuff.

My initial thoughts about documentation: - I am not 100% understand everything, yet but I see addCommand and addBinding are separated for commands. Maybe command and binding for it should...

I misunderstood bindings at first. I thought it was related to `std::bind` like it was assignment of arguments to command call etc. But is related to hotkeys logic to trigger...

Made the first attempt https://github.com/f3d-app/f3d/pull/2116

I would like to work on this issue. I was busy for couple of weeks and didn't work on my other "feature"-issue, but I would rather proceed with it slowly...

Some update on the issue. First of all it is quite difficult to exactly compare paraview and f3d implementation as paraview in general much more complicated and it seems playing...

> Which pointer is not initialized ? `vtkUnstructuredGrid.Connectivity` as it is retrieved in `vtkXMLUnstructuredGridReader::ReadPieceData()` `vtkUnstructuredGrid::SafeDownCast(this->GetCurrentOutput());` It is being cleaned normally and expected to be initialized, but call to initialization is...

I investigated a bit more and it seems probably issues is related to this fixme: ``` vtkTypeBool vtkXMLReader::ProcessRequest( vtkInformation* request, vtkInformationVector** inputVector, vtkInformationVector* outputVector) { this->CurrentOutputInformation = outputVector->GetInformationObject(0); // FIXME...

> So my understanding is that you may not have time to look deeper into this [@exbluesbreaker](https://github.com/exbluesbreaker) , should I unassign it ? :) I think I cannot work on...