FreeCAD Forum

These are definitely two different directions. But, in FreeCAD, we are free, and can take both directions at the same time. I really like the idea that, for ex, you use Draft Edit on a wall, you see the edit dots under the wall. You don't even have to care where the base wire is. We should be able t...

Yes. One concept I feel is important: The way we design the internal workings of the object, should not necessarily be the way user interface with the object. Ex, we can keep the internal base object, but users should be able to manipulate it as if there wasn't. Ideally new users should be able to n...

Arrows work for me here: https://www.freecadweb.org/api/modules.html
But its a long time i didn't recompile...

Now I imagine Werner surrounded by piles and piles of computers...

As for the "class" to the sketcher DOF text I guess you should use QObject::setObjectName() to the QLabel so that you can access later with the following stylesheet code: Great, that's very good to know. However it only works for a single widget. Most of the problems we have is with modes or events...

This musescore vid is really cool..
Musescore seems to have a fulltime dev tem, right? While we don't there are still some good things to pick... The UI is really neat

There might be a number of reasons.. But thanks for providing the file, this always helps a lot.
I'll have a try with it...

One of the things I tried at first with all arch objects is to have them simply fail silently if not all conditions are met. They simply do nothing. This helps to make them very solid and harder to break. But of course the next step is to inform the user better. That's something to start working on....

Yeah, let's brain storm, of course, it's always the best thing to do. It's a complex dependency problem... I'm not sure the "Move base" property we added is not making things worse actually. Maybe walls need to have their inner base shape removed completely and become implicit? However this seems a ...

This is indeed a defect in FreeCAD. We export almost all position vectors as 3D (3 coords). This works as there isn't apparently something in the schema that prevents it, and haven't seen any BIM app to have problems with that yet. But it's not correct indeed... As for encoding, that too is annoying...