I'm glad you've found my code useful for your tool, but would you mind to use a different icon for your measurement tool? Using the same I made for Caliper could be misleading for user's of manipulator WB.
I'm glad you've found my code useful for your tool, but would you mind to use a different icon for your measurement tool? Using the same I made for Caliper could be misleading for user's of manipulator WB.
done.
Given:Zolko wrote:
yes, I know, this is since the UI is in the Task panel: I don't know how to "chain" the commands in the Task panel, so that 1 task opens the next one. With window widgets it was straight-forward, with Task panels simply calling the next command raises an error, because only 1 task can be open at once.
I like the task panels but the workflow is now much slower. I just assembled 15 parts into one assembly and these additional actions cost a lot of time, (and I had a deadline
Place one LCS at first location for first body or fastener. You can then use an Array from the Draft workbench as shown in this example:
Yes, OK by me but takes some time to get use to. Perhaps placing the Edit button next to the Insert button would help.
Sorry to ping this, but, I'm having a look at this project today...is the answer so obvious I shouldn't ask?drmacro wrote: ↑Wed Jun 24, 2020 7:37 pmGiven:Zolko wrote:
- several FCStd files with LCS's that represent pieces of an assembly
- create new file with A4 Model
- position parts into assembly
Now:
- want to design a new part of the assembly around existing assembly (created above)
- add Part (name it thing1) with sketch, pad, etc.
Questions:
thing1 is now positioned at the world origin. Is it legit to just add LCS's as needed and do you adjust attachment offset?
Would now like to have thing1 as a separate FCStd file. Is this possible.
Hope I expressed this well...
Just trying to my head around the work flow.
![]()
![]()
Many thanks!
Code: Select all
v_x: Vector (-6.5, 0.0, 0.0)
v_y: Vector (0.0, -6.5, 0.0)
v_z: Vector (0.0, 0.0, 100.0)
n_x: 2
n_y: 2
n_z: 1
use_link: True
Part::FeaturePython / Array: Links go out of the allowed scope