2019-01-02 02:52 PM - last edited on 2022-10-04 04:46 PM by Daniel Kassai
Solved! Go to Solution.
2019-01-02 08:49 PM
GS::Array<API_LibraryInfo> libInfo; if (ACAPI_Environment (APIEnv_GetLibrariesID, &libInfo) == NoError) { API_LibraryInfo li; li.location = IO::Location ("<path to the lcf file>"); libInfo.Push (li); ACAPI_Environment (APIEnv_SetLibrariesID, &libInfo); }
2019-01-02 08:49 PM
GS::Array<API_LibraryInfo> libInfo; if (ACAPI_Environment (APIEnv_GetLibrariesID, &libInfo) == NoError) { API_LibraryInfo li; li.location = IO::Location ("<path to the lcf file>"); libInfo.Push (li); ACAPI_Environment (APIEnv_SetLibrariesID, &libInfo); }
2019-01-03 10:25 AM
2019-01-10 01:03 PM
2019-01-10 04:38 PM
n.mihaylov wrote:Properties are available for certain Classifications. So if a Property Definition is available for a Classification then all elements with the given Classification will have the specified Property.
And is it possible to create a new property group (ACAPI_Property_CreatePropertyGroup) with properties for an object that I added with the .lcf file or they should be included in the .lcf file?
2019-01-11 09:57 AM
2019-01-17 05:00 PM
2019-01-17 08:13 PM
n.mihaylov wrote:An .lcf file doesn't contain elements. It contains library parts (or objects) that describe what will happen if an element is created of that type, e.g. how it will be rendered in 2D or 3D. So you only have an element with a guid when you place an instance of a library part in the project.
Maybe a last question: what is the proper way to obtain the guid of the element that I imported from the .lcf file (in order to set its properties)?
2019-01-18 09:19 AM
2019-01-18 09:54 AM
n.mihaylov wrote:It's not true that those properties won't have value! Those properties will have the default value of the property.
When I draw another wall (new instance) - it also has this property group but the properties have no values and I have to use Pick Up/Inject Parameters from the instance I created with my addon.
n.mihaylov wrote:It's right.
If this is the normal flow, then when I import a library object and add properties for its classification (in my case Building Element Proxy but I have to find a way to get it automatically), the object is not placed immediately and when I place an instance of it I will have the properties with no values again, like in the case of a wall, right?
n.mihaylov wrote:Yes, that's right. You can use that function to set properties of an element instance (already placed).
I hoped ACAPI_Element_SetProperties would set the "properties" to the element with "elemGuid".