Display component custom attribute in model
-
Hi,
I have created a dynamic component that models a type of SIP panel for construction. When creating output I'd like to show sections of the model with each instance of the component displaying its unique identifier. The unique identifier is set by using a formula within the dynamic component. Is there anyway to display a component attribute in text on the component in the model?
Thanks in advance! -
I don't know of an easy way...
Let's assume the reference is numerical [it's just easier!]
You could embed ten pieces of flat '3d text' '0' to '9' placed on top of each other repeated laterally for the length of the reference.
And then a very convoluted automated rule that takes the reference-code and deconstructs it into its numerals, and then displays the required numeral in each position - like the old fashioned signs in the railway station that display various numerals from a rotating set... You could do it with other characters like letters, but then the permutations go up alarmingly I can't see a simple way. -
I've seen digital LED type DC's on here that would be a variation of what Tig is talking about...
You can set the text the user sees in the DC Options, and you can set an "alert" onclick function for any component -- and for that matter you can export that information as a spreadsheet... but getting text in Sketchup space seems to require more than DC can give in their current form.
Best,
Jason. -
Ha! Thanks for that suggestion - so crazy it just might work! I was hoping that there may be a ruby toolkit that could do it in a programmatic way.
-
Apologies for the stream-of-consciousness posts - but is there some way to make an auto-incrementing identifier as a custom property of a dynamic component instance? I was using a complex identifier made up of the z-x-y co-ordinates in inches, but this produces 11 digits where probably 3 would do. The corresponding complexity of the 'digital clock' display becomes problematic.
-
Quick test reveals that this is a feasible approach. I'm a little worried by the exponential increase in the number of components in the model, but I'll have to test and see whether that kills the performance.
I'll put up the sample when its working.
Advertisement