The fact that the two mentioned tools are part of BIM toolbars, which is what I meant (obviously ), must mean that they are useful and can be used.
So this sweeping statement still seems incorrect to me:
The fact that the two mentioned tools are part of BIM toolbars, which is what I meant (obviously ), must mean that they are useful and can be used.
It's not a sweeping statement, it's a general recommendation for new users. It's like those users that start mixing Part Workbench operations with PartDesign operations. It may work some times, but other times it creates chaos. If you are an experienced user, then you already know the pitfalls, and what works and what doesn't; this all comes with experience. Newbies need to be invited to follow best practices.
The problem is, as a newbie, I'm assuming that all the tools I see in the Arch workbench by default are good to use for arch stuff.. if this doesn't hold true, maybe they should not be shown by default in that workbench? Or am I expected to know which workbench the tools are actually from, and then only use those that are from Arch (which means I mostly cannot actually do any work :-/)vocx wrote: ↑Fri Sep 13, 2019 7:37 am It's not a sweeping statement, it's a general recommendation for new users. It's like those users that start mixing Part Workbench operations with PartDesign operations. It may work some times, but other times it creates chaos. If you are an experienced user, then you already know the pitfalls, and what works and what doesn't; this all comes with experience. Newbies need to be invited to follow best practices.
This is both a characteristic of the system (open source development, everybody does what they want), and of the user (users will try to use tools however they want, no matter what the system or documentation says).
This could be approached by providing more documentation and tutorials, which for Arch, there are quite a lot online.Or am I expected to know which workbench the tools are actually from, and then only use those that are from Arch ...
Ultimately you have to recognize that FreeCAD is a complex system with many, many tools in many workbenches. It is difficult to handle everything at the same time in a 100% coherent manner. And the same thing exists in commercial CAD systems; they have hundreds of tools to do a variety of things. Some of those tools may also conflict with each other, or lead to unsatisfactory results. In particular, in CAD it's the opposite of the Zen of Python.yorik wrote: ↑Tue Jul 09, 2019 3:13 pm Excellent!! Also very similar to the tutorial tool i am doing for the BIM WB.... I'll have a better look at yours
This kind of tool can have a huge impact on FreeCAD leaning
Well, you already saw the problems in this thread about the Window, and trying to cut a wall with Part Cut. Boolean operations like that aren't ideal with Arch objects.
Thanks. I guess this is the tutorial tool I was talking about.Roy_043 wrote: ↑Fri Sep 13, 2019 9:17 am Maybe this is useful:
https://www.freecadweb.org/wiki/BIM_ingame_tutorial
OK, so a cut is not recognized as a wall. I would not call that a problem. I can think of examples where you would have to use tools from another WB. F.e. a wall with a niche with filleted edges.
It is a "problem" if the user creates a thread saying that "it doesn't work", id est, this thread.
Yes, that's a possibility. But you could also design the trace first with say, Draft or the Sketcher, and then create the Wall. You don't have to fillet the actual solid of the wall.I can think of examples where you would have to use tools from another WB. F.e. a wall with a niche with filleted edges.