Nice for #FreeCADux to show the command. This, however, requires context switch to this particular problem.
Update: Next day the Construction Geometry was visible for once o_O
2/2
Documenting #FreeCAD v1+ #UX problems & possible solutions, to enable & encourage improvements, while learning – on this instance.
– AI/AGI instance: https://sigmoid.social/@HuK
– #Infosec, #linux, #debian https://infosec.exchange/@HuK
– Other/generic topic instance: https://mas.to/@HuK
#AI/AGI positive Cognitive Scientist, Independent Researcher. #CogSci. #AGI, #AI. Machine Learning. In Helsinki, FI, EU, The Free World
🇫🇮🇩🇪🇸🇪🇪🇺🇨🇦
I HAVE OTHER ACCOUNTS FOR TOPIC BASED FOLLOWING:
Nice for #FreeCADux to show the command. This, however, requires context switch to this particular problem.
Update: Next day the Construction Geometry was visible for once o_O
2/2
Slight bug in FreeCAD v1.0.1, when Tool / Addon Manager -> "Assembly 4" -> Install or Update:
Dialog shows..
git clone --recurse-submodules https://github.com/leoheck/FreeCAD_Assembly4 ~/.local/share/FreeCAD/Mod/Assembly4
..fails.
The failure results in directory with .git files.
Workaround: rerun the command manually
– rm -rf ~/.local/share/FreeCAD/Mod/Assembly4
– git clone --recurse-submodules https://github.com/leoheck/FreeCAD_Assembly4 ~/.local/share/FreeCAD/Mod/Assembly4
(In Linux AppImage; I think flatpak also)
1/2
After flatpak update, #FreeCAD v1.0.0 upgraded to v1.0.1. Nice.
However, activating the FCGear Work Bench resulted in "No module named 'scipy'". FCGear was not activated.
After flatpak uninstal & install, no more this error. FCGear is activated.
3/3
Perhaps I cannot go back and forth with different LCSes and one off works.. For now. Or something.
2/*
2) I cannot use other / at least Part level LCSes (LCS_metacarpal2_carpus) for later features in the same Body.
I.e. after harmonizing Groove004 & Sketch_metacarpal2_proximal_anterior_pingroove attachment to Body LCS (LCS_Body_metacarpal2), the whole solid works... For now...
However, I still have Sketch_metacarpal2_wiregroove Attached to Part level LCS_metacarpal2_carpus . This is the only non LCS_Body_metacarpal2 attachment in this Body.
....continues...
On FreeCAD v1.0.0 with Assembly4 & PartDesign Body, it seems, Local Coordinate System (LCS) visibility context is weird, at least non-global...
Or, to make LCSes global, should I put them in the Assembly or high in the hierarchy?
Strange visibility/"non-solidity" issues appear in LATER, if too Attachment LCSes change too much, in the feature hierarchy. Or something.
Case:
1) When I use the Body LCS to Attach/position earlier features in the Body,
1/*
FreeCAD v1.0.0 UX inconsistency (on Linux):
Sketch Attachment cannot be exited with Esc. You must ALT-c.
I wish #FreeCAD Spreadsheets had alignment to left.
It would be visually faster to browse through the variable names, grouped by the same prefix.
FreeCAD pain to access crashing document
I'd need to change value in Spreadsheet.
There should be command line option to disable recompute on document load.
Geom_BSplineCurve: Weights values too small
Program received signal SIGSEGV, Segmentation fault.
#0 /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x7f4bb5279050]
#1 0x7f4b7a83ec60 in Geom_TrimmedCurve::Geom_TrimmedCurve(opencascade::handle<Geom_Curve> const&, ----
#FreeCADux #FreeCAD v1.0.0 & 1.1.0beta build 41573
Wow, #FreeCAD Spreadsheets is awesome compared to VarSet! (had to go there first I guess, LOL)
Renming Aliases populates to models automatically. No need to edit dependent Constraints!
This is a huge help for constructing, refactoring, and editing the model – by using Spreadsheets.
Inserting Rows and renaming Aliases enable this 🙂
Keyboard shortcut wishes for #FreeCAD, random:
– Move between Model, Task, and Python console bars/tabs with ctrl-PageUp/PageDown.
– Sketcher Constraint shortcuts: edit if exist (instead of create)
Mnemonics for:
– Attachment mode right-clicking (this works though: 2* arrow-down, Enter)
– consistency e.g. between OK some dialogs and Close Sketcher in Task.
– reloading doc/object
I just passed SpreadSheets, when I started learning #FreeCAD and went with VarSets.
Risky move?
The there was a bug (or could it be configuration issue) with font foreground color being white like the background, https://sw-development-is.social/@HuK/113969027695626531
Now, to think of it, SpreadSheets would offer comment column and other stuff helping refactoring like variable naming not available with VarSet.
Just started to generate ~156 parameters with Python to VarSet... Or maybe I should go w/ Spreadsheets?
I just passed SpreadSheets, when I started learning #FreeCAD and went with VarSets.
Risky move?
The there was a bug (or could it be configuration issue) with font foreground color being white like the background, https://sw-development-is.social/@HuK/113969027695626531
Now, to think of it, SpreadSheets would offer comment column and other stuff helping refactoring like variable naming not available with VarSet.
Just started to generate ~156 parameters with Python to VarSet... Or maybe I should go w/ Spreadsheets?
Console print index numbering bug in #FreeCAD
The graph must be a DAG.
Recursive calling of recompute for document bearing_d34_90deg_turned_locks_for_thinner_rollers
bearing_d34_90deg_turned_locks_for_thinner_rollers#PolarPattern016 still touched after recompute bearing_d34_90deg_turned_locks_for_thinner_rollers#Mirrored015 still touched after recompute
Boolean010: Result has multiple solids: that is not currently supported.
Image. DOM ID's have indexing +1 as in Mirror016 and PolarPattern017.
Reflections on working with #FreeCAD & VarSets & notes to self, after finishing one iteration of 3D printable roller/ball bearing:
– strive for long consistent variable names; it's hard to recall local context
– try to think in one coordinate system when naming variables
– avoid helper variables. You don't recall them
– put the logic in Constraints; copy paste when needed. The 3D view is anyway the place to get the visual cognitive support for recall, reasoning, and design work.
I'm working on my roller-bearing. Tweaking physical parameters based on first 3D prints.
I wish I could have on-screen visibility and scrollability of VarSet, when I'm working on the 3D view, Sketches, solids etc.
I keep forgetting my variable logic in VarSets. Cognitive load is substantial.
Then I resort to copy pasting expression values between constraints.
This is my first major project (2nd part). Still learning best strategies, while also hoping for better UX to help #FreeCAD
Thanks.
Parametrizing with VarSets and Sketch Constraint values, much of the design work is arithmetic on the expressions.
First I tried to put everything in VarSets. But then forgot my logic there.
Then I started put the expressions in constraints, because GUI hints the recall.
Then I had the need to copy paste these exp's. And this click path could be shorter.
The grain of salt: I'm self-thought with FreeCAD in my own bubble, so I might not have the optimal way to do things.
AND #SubShapeBinder does not combine with Pockets nor Boolean Cuts..
waddafaaak-- #FreeCAD
So I'm doing a bearing. Have 2-part cage, with common Bodies, inherited with SubShapeBinder, (which also needs to be made solid with Boolean Fuse ok).
HOWEVER, the #SubShapeBinder is not freely editable: it needs to be created/inserted at the tip of the Body hierarchy.
Result: child Bodies cannot be updated, alas, because the topology breaks 😢
WORKAROUND
Create dedicated minimal Bodies for SubShapeBinder+Boolean Fuse only stuff. This eases their recreation on change.
What if #FreeCAD had:
In Sketch right-clickable "copy expression"?
That would reduce click path a lot.