Happy candy season all!
New extension just dropped. This one lets you easily write descriptions for your selected component, without having to open the Conponents Panel, go to In Model, locate the component in the list and hit Edit.
Happy candy season all!
New extension just dropped. This one lets you easily write descriptions for your selected component, without having to open the Conponents Panel, go to In Model, locate the component in the list and hit Edit.
Very nice. Thank you!
I like that it includes carriage returns that carry over to labels in LayOut.
May I make a request? Could you add an option to automatically include the componentās Definition Name and perhaps Instance Name if it exists? The user could then either edit that text and/or add whatever other text they want to include. The default would be like this:
Definition Name,
Instance Name,
From there whatever the user wants to add can be put in.
BTW, I know some of this can be done with the auto text for labels but it would be nice if it could all be combined into a single auto text field.
Iām considering adding definition and instance name, but they can already be controlled in Entity Info so I donāt know how much itās needed
Is this limited to a single definition or can I assign the same description to multiple definitions at the same time? I am thinking of very similar components where the description might be the same e.g. different length beams.
True. Iām just thinking of making it easier to include that information in labels in LayOut. Would only need the component descripition auto text tag instead of multiple auto text tags as you do now.
It looks the content is stored in the dialog, separate from the Component attributes. It would be a nice feature to have the data import to the component description attribute, and if multiple components are selected let the data write to multiple components. Maybe with an added apply button. If multiple writes would be too problematic then at least the one selected would be nice.
No actually, this extension is about the native properties of Component Definitions.
You are confounding this with Dynamic Component attributes.
DC is a Ruby extension that saves data in attribute dictionaries not native C++ properties.
Thank you Dan, I am trying to learn, this is exciting to me. I am working on a dynamic component that I was trying to control and display data, much like the attribute pop up, but with more detail and control in both directions. Eneroth3 has a unique way of targeting the component. I was able to control the component from an html dialog, but next trying to get the dialog to read from the current state of the component. Here work looks promising. :
On my Flange Options dialog I am hoping to get the current state of the dimension callouts that are shown in the Options pop up. Then I would not need both pop up and dialog open. I apologize, I did not intend to hijack your post Eneroth. your extension is very clever work. Nicely done.
It would be nice to have AutoText as part of Sketchup. I see how they pull the name of the part already, but if we could maybe use ā<comp.attrib>=valueā in a label and have it pull from the component definition attributes and values inside SketchUp, and be usable in Layout as well. If this could be feature part of Eneroth extension would be awesome.
You can get a lot of that information in Labels in LayOut. Hereās an example from aDC I built for a client. This is all of the atributes for the drawer box component.
Iām thinking it could be difficult to reference another property in the text and have it update when that property updates.
Iāve considered editing more than one component definition at a time but it adds a bit of complexity in how to handle components with different descriptions being selected. For now itās limited to one definition at a time.
OK. Understood.
I had actually proposed something similar to this several years ago for all component definitions.
Currently, (I think) the exposure of definitions in LayOut are hardcoded and limited to the "dynamic_attributes"
, āSU_InstanceSetā
, āSU_DefinitionSetā
and IFC dictionaries.
I asked for a way to specify the name of the dictionary and attribute: <dictionary["name"]>
or similar.
It would be best to start your own topic in the Dynamic Components subcategory.
Hi, Thank you for all your extensions.
A question about this one; will it work for SU2021?
2021 wonāt open the extension warehouse anymore, so i have to get it from somewhere else.
The EW page lists 2021 as supported.
Incorrect, you get it from the EW, but you open it in an external web browser and download the RBZ manually. Then you install it via SketchUpās Extension Manager by clicking the blue āInstall Extensionā button (at the bottom left of the EM,) navigate to where you saved the RBZ archive, select it and click Open. The extension should be installed. Usually, you would restart SketchUp so that the new extension loads normally with all the rest.
Havenāt tried this extension as Iām still battling with 2018 (though licensed for 2021) as Iāve opted to bypass subscription and the upgrades from 2018 to 2021 havenāt tickled my fancy..
However JCE, Iād like to take the opportunity to sincerely thank you for all your contributions to us SketchUp hacksters that your plugins have made our lives sooo much easier.
THANK YOU!
Tried this, added text, but where do I apply these? When I close the popup the description in de components panel is not changed