yorik wrote: ↑

Wed Apr 10, 2019 8:10 pm

Anyone mpi-enlightened around?

I don't consider myself particularly enlightened, however the cMake documentation seems to suggest that the following change would result in the behaviour you describe:

hardeeprai wrote: ↑

Mon Apr 15, 2019 2:12 pm

Both these files are not there

What do you see when you issue the following command?
What version of python do you have installed? What does the following command show?

Likely this: https://forum.freecadweb.org/viewtopic.php?&f=10&t=27582&p=225338#p225338 Yes that's it! incidentally, I probably need to update the links in my original posts I fixed some, just needed to re-upload the appropriate branch to my github repo. If anyone tries to use one of my links and it...

The const keyword is a great feature, especially for C++ classes. Unfortunately, many developers don't use it only because of laziness and thus they don't benefit from its advantage. The point is when using it properly then it reduces a lot of possible side-effects which in many cases the compiler ...

triplus wrote: ↑

Thu Mar 28, 2019 5:27 pm

Indeed i remember you have mentioned this in the past, that you have tried out the OCCT TopoNaming solution.

I was trying to find the post where I talked about the issues I had with TNaming, but I couldn't find it

With regards to OCAF and Topological Naming, or more specifically the TNaming framework that OCC provides, I think I can provide a bit of insight (or at least some personal thoughts/opinions). My initial approach to the topological naming problem was to do as you have suggested and utilize the exist...

What I mean by "in the long run" is "as the code base grows and ages". There are many times where you know exactly what you mean when you originally write a function, but months/years later, when you're not thinking about it, you end up mis-using it. This can be avoided by being more explicit in you...

PS Incidents like this make me think that adding 'const' to the C++ language was of a dubious advantage at best. Not to get too "political" here, but the 'const' feature in C++ is a good feature when used correctly, and helps to ensure clarity in code as well as non-ambiguous interface definitions....

since your interest in more on the Coin3d stuff, I would instead start at Mod/Part/Gui/ViewProvider. h, which describes how a Part:Toposhape is rendered using Coin3d.

Not sure if you're aware, but if you `make DevDoc` in the freecad build directory, it will generate the Doxygen documentation which includes dependency graphs for the various freecad components. This has been helpful for me in terms of seem how the code is structured. Mod/Part/App/TopoShape.cpp is a...