Again I want to say this is not a bug but just a heads up only.
have you thought about using a menu structure like this ?
does that mean that the script should analyse a self designed part how much all the needed fabrication steps will cost or only adding costs of catalog parts as screws, bearings or something like this?
the part data are under file properties and as far as i know this data could not be pulled via alibrescript.
Its undocumented and unsupported but the Alibre API can be used.
https://www.alibreforum.com/forum/index.php?threads/script-release-total-cost-center.21360/
The API Help documentation can be found on the bottom of the Alibre Home window Explore tab. I think the dll has been included in most Alibre releases for addons to use.
sarcasm mode off...
#subtotal = Cost(ThisOcc, total) change to:
total = Cost(ThisOcc, total)
print('\n### End SubAssembly: ' + str(ThisOcc.Name))
total = float(total) #remove: + float(subtotal)Thanks! You are correct I started with code from something else and I was too tired when I uploaded.But here something to the script:
Would it be better to change the additions to only "total" to get a correct result for grandtotal?
(I've made a testrun with 1 toplevel part and to subassys with 3 parts each and got a wrong grandtotal...)
Regards
Stefan
I should not have needed to pass the total in the function. #subtotal = Cost(ThisOcc, total) change to:
subtotal = Cost(ThisOcc)
You do (I hope) realize that you can SaveAs the Script and then Delete it from the Part or Assembly file?? -- Lew
for what purpose? You can save it as a protected script with a self written password function, but if you use the Part Properties to store the cost values you only need to add them manually to get the result (except they are crypted;-)) Do you really have a need for this?
