(SOLVED) Arch_StructureTools: the order of operation decides whether it works?

[thomas-neemann]

if i first select beam and then enter the dimensions, an entry is ignored, it works the other way around. Can anybody confirm this?

test15sep.FCStd

(9.59 KiB) Downloaded 22 times

https://www.youtube.com/watch?v=tY3p5ICOTqs

phpBB [video]

Code: Select all

OS: Ubuntu 20.04.1 LTS (XFCE/xubuntu)
Word size of FreeCAD: 64-bit
Version: 0.20.1.29410 (Git) AppImage
Build type: Release
Branch: (HEAD detached at 0.20.1)
Hash: f5d13554ecc7a456fb6e970568ae5c74ba727563
Python 3.10.5, Qt 5.15.4, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.2
Locale: German/Germany (de_DE)

[Roy_043]

When switching from column to beam the length and height values are switched. The height of the column becomes the length of the beam.

[thomas-neemann]

When switching from column to beam the length and height values are switched. The height of the column becomes the length of the beam.

thanks for the information. That's probably an operator error on my part

[yorik]

This thing of length and height switching is really bad design... But so far I couldn't think of a better idea. I thought we should call it "extrusion length", but in a BIM world, concepts of length and height are important. And if we have length and height properties, the same issue will happen anyway, their values will "switch" depending on the orientation of the object.

A solution could be to physically separate beams and columns into 2 different objects, but i see that's what commercial BIM apps do, and not doing this gives us a great deal of flexibility...

That said, there have been recent work on the Arch Profile that now allows a FreeCAD Arch Profile object to change its python class... This could maybe be of good use here, an we could afford two different classes.

[thomas-neemann]

...

Thanks for the feedback. I think such an improvement is good, I would have almost created a faulty construction if I hadn't checked everything again at the end.