Forum Replies Created
-
Posts
-
Here is a short guide to deal with the properties: https://gdl.graphisoft.com/tips-and-tricks/display-properties-with-labels/
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGeoff,
Sorry for the problems, but I can’t predict when we can correct this bug. Besides the previous workaround, I don’t have any ideas how to avoid it in GDL.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHi Naraindrra,
Why do you want to use text2 or print in a property object? These object only used for listing, so I can’t imagine why they should use those commands.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHi Guys,
Barry got it right: GDL scripts contains the name of macros, and when you save an object then AC looks for that by it’s name, and saves the macro’s GUID to the caller object. If you have more than one macros loaded with the same name, then the behaviour will be unpredictable: AC will use the first object with the name – and store it’s GUID to the caller. And yes, it can change save by save, depending on million things.
So the proper way of developing any libraries is to do not have duplicate names with libparts/macros loaded together…
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThe line success=req(“WALL_SKINS_BMAT_NAMES[1]”) is absolutely useless, first try to delete it. If it does not help, then send me a sample file in mail please.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGLOB_VIEW_TYPE should not be used in parameter script (and in master when it runs as paramscript) – as it is a view dependent variable.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEYou can create a property object, and link that property object to the zones. In the property object’s property script you can reach the zones parameters with “ASSOCLP_PARVALUE” request, and calculate anything based on that, and list with the old listing as components.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHi,
It seems a bit strange, but if you send us a pla, we can try to investigate that. By the way I strongly suggest to avoid macro name storing in variables and calling placeable objects…
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEYou’re right, it would be much better if we had a common parameter for detail level settings for all the elements, but unfortunately we do not have. It would be a quite big project to do that for all the elements with proper migration, and it is on my list but I don’t think it will be released soon. 🙁
Now mostly we use the gs_detlevel_3d/gs_detlevel_3d_m parameter pair, with the values “Detailed”, “Simple” and “Off”.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEUnfortunately there is no request for skylights’ markers visibility.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThose requests does not exist in GDL. Zone stamps can reach many informations with fixed name parameters as it is listed here:
https://gdl.graphisoft.com/reference-guide/room-parameters/Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHi Daniel,
I’d like to know more about the workflow between those library parts: why do you need text files, and how do you use them. If the files can not be published here, then you can send me some samples in mail (to gdlcenter@graphisoft.com).
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEParameters can only be updated from parameter script (or the master script when it is running as paramscript). In a situation like this, the less painful solution is to put the calculations to the master – if you can’t avoid to store the number of seats in a parameter.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SELibparts can be simply copied and used in any projects, maybe an add-on can protect libraries. The only protection is the password setting to hide the scripts and avoid changes in your libparts.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE
