at the moment the imported part are not parametric as they are a "screnshot" of current original part.
- Thanks for clarification! My programming knowledge at zero level, so I can't understand much. I look to the question from the practical side. If #PARTINFO# could just see correct values from #PARTINFO#(s) - that's super for me at this time...
I tried also to write some parameters to #PARTINFO# straight from the part element using "Pad.Length"-formula bypassing of spreadsheet using (look the screenshot) - no result. My thought is: may be there's some logical function in a spreadsheet, which lets to convert a formula to digit, that #PARTLIST# could understand...?
During refresh, the original part can be copied to a temp file, recalculated by taking values present in the part tree in the assembly (which are now customized) then imported as usual, once successfully updated the temp part is discarded and the original is left unchanged avoiding conflicts with other assemblies. How about this? it could be an option?
- Sorry for misunderstanding, If I get things right you mean the possibility to correct the part's values inside the assembly bypassing the corrections of the external original imported part? I'm not sure this could be a comfortable idea. My position is that the main assembly could make "screnshots"(as you've mentioned) only from original files, that are "linked" (sorry for my terminology, if it's not correct) to the assembly. Otherwise, if you will want to reuse some parts from your assemble - you'll need some export function from the assembly, because the original files can have not the same values as in the assembly. And so you can just copy library's parts to your project folder, import to the assemblies, modify them and A2Plus will join them as they are.