Thank You @hatari for your kind advice.
Herebelow some explanation of some of the points. I'll work on the others as soon as the stable release 0.18 will be issued.
hatari wrote: ↑Mon Mar 11, 2019 3:01 pm
Qt-issue: FC crashes when FrameManager is open and you first select an existing structure created along a sketch and then click in "the void" i.e. somewhere in the graphic window and don't hit another structure element.
That is the most work for next months because I have to change some syntax when calling PySide function.
I just wait to get the 0.18 official release.
hatari wrote: ↑Mon Mar 11, 2019 3:01 pm
I can't reproduce exactly when, I think it is usually when saving the file it works but I get:
Code: Select all
Traceback (most recent call last):
File "/usr/lib/python2.7/json/__init__.py", line 244, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python2.7/json/encoder.py", line 207, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python2.7/json/encoder.py", line 270, in iterencode
return _iterencode(o, 0)
File "/usr/lib/python2.7/json/encoder.py", line 184, in default
raise TypeError(repr(o) + " is not JSON serializable")
<type 'exceptions.TypeError'>: <method 'changeAttacherType' of 'Part.AttachExtension' objects> is not JSON serializable
I also noticed that when reopening a file with a PypeBranch in it. I guess it's something related how the PythonFeatures are saved inside .FcStd: something outside my horizon.
Anyway this won't produce any issue while working, at least in my experience till now. So you can ignore that alert.
hatari wrote: ↑Mon Mar 11, 2019 3:01 pm
[*] Sketch based Profile: if I use a custom sketch and draw a closed hollow profile to use for my structure, it is filled also in the inside.
[*] Sometimes, if the direction of your custom profile sketch is orientated in the wrong way, the "reverse orientation" command is reset after you make changes to the path geometry. Is there a way to prevent this or is it due to topological naming?
Up to now, the problem with hollow sections must be solved by using Draft objects instead of sketches. Draw two rectangles and subtract one from the other.. and also pay attention to the "direction" of drawing because if you use DWires you must draw the lines in the counter-clockwise direction! As you already pointed out, that seems strange but it's actually how the geometry used in FreeCAD affects the features. The workaround could be to add some "if" clauses to check the orientation of one surface before extruding, but it's a bit cumbersome in the code and I'm lazy
In previous versions of flamingo I used the function "makeProfile" from Arch workbench also to create hollow tubes but lately I found that it do not work because it subtract the outer rectangle from the inner. (@yorik, did you notice?)
hatari wrote: ↑Mon Mar 11, 2019 3:01 pm
[*] If you join edges in order to position structures and then trim/extend them, after this operation the position of the profiles is reset. Bug or feature?
maybe because you use the trim button in the toolbar to modify a beam belonging to a "framebranch": like "pypebranches" they are hard-linked to the .Base underneath (DWires or Sketches) so they are always recomputed according the length of the edges. That won't happen if you have a loose "Structure" object or if it is included in a "frameline" group, instead.
To trim the beams belonging to a framebranch it's necessary to use the buttons in the relevant dialog: [Get targets] (to select the cutting edges: also with multiple selection to perform the action at both ends) and [Trim/Extend]
hatari wrote: ↑Mon Mar 11, 2019 3:01 pm
[*] Nice to haves/Feature requests
Have you ever thought about a tool that lets you choose how your profile will be aligned to the structure path like common commercial Frame Managers have? (for example like shown here:
https://www.youtube.com/watch?v=QfDS_gCP_s0). Would that be even possible?
screenshot9.png
yes. Making a dialog to create customized sections is in the TODO list for long and I think now it's time to implement.
hatari wrote: ↑Mon Mar 11, 2019 3:01 pm
[*] Is there a way to make parametric miter corners with a bisect plane in situations like this?
miter.png
[/list]
as @engdham says, I looked inside the Frame workbench but I still did not found a good solution to integrate: the matter is that all commands in flamingo are suited to work with object that have some specific properties in their class definition, similar to Arch.Structure, while that workbench defines a new FeaturePython to make the head and tail ends "trimmable". Maybe in future I could find a good strategy to include also the objects of Frame wb.