Forum Replies Created
-
AuthorPosts
-
Gergely FehérKeymaster
Hi!
Accessories are dead end in many ways, we still do not want to develop them further in the future. It is a an outdated and limited technology, from the past, where modelling and bim tools were much more simple. As they still can be used with single plane roofs, and simple walls/slabs without priority based connections we did not kill them, but we won’t spend any time on them except of minimal maintenance.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi Bruce,
You can not and should not reach any data of a profile from parameter script (including master, when it runs before parameter script). If you would be able to do so, that could cause inconsistent data in a plan file, as you can place an object using profiles, after that if you change anything in the profile that won’t be followed by a parameter script run, so your object could easily store outdated information or invalid, inconsistent data.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi,
I’m not sure about the purpose of this request: custom door leafs are used as they were saved, except they are streched to the proper panel size. You have no control of anything inside of the component, so I’m not sure what you exactly want.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi Chris,
If you open the object editor and change the parameter values, that only affects the default values of the object (door, window…). To edit the values of a placed instance, open the settings dialog, go to the graphical ui part (Hinged door settings in most of our doors), and search for the minimal space tabpage (usually second from bottom) – there you’ll find all relevant parameters for minimal space.
Attachments:
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterCheck the samples here: https://gdl.graphisoft.com/tips-and-tricks/model-view-options-in-general and here: https://gdl.graphisoft.com/tips-and-tricks/custom-made-model-view-options-object
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi,
1. LIBRARYGLOBAL should be used in 2D and 3D scripts. If you put it to the master script, you should limit the usage with a condition using GLOB_SCRIPT_TYPE.
2. If you are reading the proper paramvalues of the MVO object in 2d and 3d scripts with LIBRARYGLOBAL, you’ll always get the values for the current view. Do not need to force anything…Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi,
LIBRARYGLOBAL is a function that should be used in 2d and 3d to reach the parameter values of an MVO dialog, and change the object’s behaviour based on that. It should not be used in parameter script, and it does not make any effect on parameter values of placed objects.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterI think if there in no wallhole/wallniche commands in 2d, AC automatically thinks it should create a fill for the windows’ 2d. So I suggest to create a simple symbol for your object.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterI think if there in no wallhole/wallniche commands in 2d, AC automatically thinks it should create a fill for the windows’ 2d. So I suggest to create a simple symbol for your object.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi,
What do you mean on “I can’t use this function”? In what libpart type, and what script type? What do you mean on “read the ID of doors”? Read from a label? Property object?
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterThe “Z” direction is always perpendicular to the curtain wall. The junction element only knows this, and the numer of frames at it’s anchor and their direction. Everything should be calculated based on this. Creating a series of elements shown on the images seems to be easier with accessory elements.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterNo, you can not store the GLOB_WORLD_ORIGO_OFFSET in library part parameter, so it can not be scheduled as libpart data.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterYou can reach the IFC properties with requests, check it here please: https://gdl.graphisoft.com/tips-and-tricks/display-properties-with-labels
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterAs I checked the bug database, it is corrected for AC22.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGergely FehérKeymasterHi Kristian,
Sorry for the late answer, somehow I missed your question. So, transformation made in a macro does not affect your local coordinate system in the caller object. There is a solution to use that transformation: at the end of the macro, pass the 2 values back to the caller, with “end tblock_wid, tblock_dep”. In the caller, you can receive these values with “returned_parameters tblock_wid, tblock_dep”, and write the transformation in the caller.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE -
AuthorPosts