Silvio Traversaro

Even if at the moment no one is interesting in working on this (hence the "Help Wanted" label) this feature could be convenient for users that have their own custom...

Good point. This is a nasty effect of the fact that `.FromPython` method is a function that returns a new instance of the type, instead of populating the instance on...

An alternative may be to define a `.FromPythonInPlace` method for `iDynTree::VectorDynSize` (better name suggestions are welcome) that populate the existing vector instead of returning a new one (a bit like...

Recap: if I understood correctly, this is an inherit limitations of macOS and Cocoa-based OSs, in the sense that windows can only be created by the main thread, and not...

As I think back to this problem, I think the only workaround for this is probably to also provide a network/IPC/RPC wrapper of some kind for all the visualizer API,...

cc @nunoguedelha

This problem today affected @DanielePucci .

Ideally, we should add the IPOPT binaries to the AppVeyor tests to automatically catch this regressions.

We had a discussion on this issue today with @randaz81 and @elandini84 . I shared with them this pseudocode: ~~~cxx if (mode == SHALLOW) { // In shallow mode, we...

The change seems to be nice, however from what I understand it is a breaking change, right? I mean, now the code: ~~~ material = iDynTree.Material() color = iDynTree.Vector4() color[0]...