New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assembly breaks #574
Comments
There is a bug in dependency tracking of referencing aliased cell in external spreadsheet, and is fixed in the above referenced commit. The assembly constraining element missing problem is tougher to solve, though. Because the mutated shape binder actually contains new geometry that has a mutated history, which can't be used for tracking topo name changes. The recommended way right now is to wrap any mutated shape binder with an assembly, and manually create its constraining elements. Note that the element of an assembly is meant to be used by upper assembly to avoid topo naming problem in the first place. If you want to get really fancy, you can make an assembly with configuration table, and bind the element link reference as configuration settings. The video below shows how to bind an expression to element LinkedObject. Please note that there is a bug in the current release preventing this from working. Please try that in my next release. Also, you are supposed to link (rather than using shape binder) the sub-assembly, and turn on its Peek.2021-04-26.15-46.mp4PS. I've also fixed frozen shape color problem. Thanks for the report. Next time, please open a new issue for a new problem. It would be easier for me to track. |
Thank you for attending the issues and for your detailed response. I will test it with the next revision and next time open separate issues. |
Hi Realthunder, I followed your excellent instructions and adapted my test project. These are my findings:
(I did not yet try your suggestion to make an assembly with configuration table, I need more time for that.) Below a short macro to replace the linked object by an expression. As I did not find out how to disable the read-only bit from python (I am not a programmer and python is a snake for me), one has to diable the readonly first then select the elements to be trated and start the macro. No error checking so I consider it as proof of concept. It worked for my projects but as I do not have the background knowledge I do not know whether it would work anywhere else. Thank you again for your effort.
OS: Debian GNU/Linux bullseye/sid (KDE/plasma) |
Somehow I have repaired the model, now it works. At first I tested the model attached above with today's daily revision and saw the same behaviour as before. Then I realized, that the expressions in the linked object fields of elements have disappeared. After generating them again, everything started working as expected. Thank you for your effort, I close the issue and attach for reference the working model. OS: Debian GNU/Linux bullseye/sid (KDE/plasma) |
OS: Debian GNU/Linux bullseye/sid (KDE/plasma)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 2021.412.22506 +5327 (Git) AppImage
Build type: Release
Branch: LinkDaily
Hash: d41e78fe7f9b54eea5977df0a7344331f08445e8
Python version: 3.8.8
Qt version: 5.12.9
Coin version: 4.0.1
OCC version: 7.4.0
Locale: German/Austria (de_AT)
Hi Realthunder,
While investigating the possibilities regarding parametrized design using configuration tables and sub-shape links I ran into some issues. Attached is a project file to illustrate. This is the concept of the project :
I observed the followng issues:
Is there anything on user side to be done for improvement?
Regal_05d.tar.gz
Two more questions:
I noted that when an assembly is frozen, the colors diappear. Is this an intended behaviour? If yes may I suggest to change this and to display the colors as set.
I observe strange rendering problems. They do not change when I change the rendering related display settings, see screenshot.
thank you for reading
The text was updated successfully, but these errors were encountered: