Forum Replies Created
-
Posts
-
Hi,
In GDL objects the parameter list is fixed, you can not add more parameters to it from scripts. “NEWPARAMETER” command works only in backward migration, when you add parameters while saving your plan back to a previous version.
The solution is to set a limit to your “n”, and add all the parameters to your objects parameter list and then hide the ones you don’t need when “n” is less than it’s maximal value. Take care, that the total number of parameters can not exceed 1024 in version 19 (and I think in 18 too).Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHi,
Getting the number of skins can be done with a do – while code block, as there is no dedicated global for it in these 2 element types. Unfortunately there is no global for the used building materials like WALL_SKINS_BMAT_NAMES.
nSkins = 0 do success = REQUEST ("COMPONENT_VOLUME", nSkins, skinVolume) if success then nSkins = nSkins + 1 while successGergely Fehér
Team Leader, Library Team
GRAPHISOFT SEDerek,
Let me check that object, please send it to me to gdlcenter@graphisoft.comGergely Fehér
Team Leader, Library Team
GRAPHISOFT SEDerek,
I made a simple test object, a new zone stamp. I added a new parameter “myArea” (a realnum) to the paramlist, andtext2 0, 0, myAreato the 2d script andparameters myArea = ROOM_AREAto the parameter script. With this I tested a placed zone, and if I moved any of the zone’s hotspots the area text is changed, so paramscript has run. If I edited the zone with a marquee, then the text has not changed – so in this situatuion the paramscript did not run. This second case with the marquee is a known issue, we are working on a solution for the next main version for that.
You can force the parameter script run with opening it’s settings dialog and closing it with “Ok”.
If you have any other workflows which changes the zone and does not change the parameters, then please report it to me. Thanks.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEJoachim,
Parameters commands only executed when the master script runs as a parameter script – before then paramscript itself. In all other contexts paramscript commands like parameters or values are skipped. (Just a note: in a teamwork situation, when a floorplan is drawn and master script and 2d script runs, you don’t have the right to change the object parameters. To be able to change the parameter list of an element, you need to reserve that first.)Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEDerek,
your parameters are not refreshed, until paramscript is not running. How did you change your zones? With the update zone function, or editing the hotspots on their contour or editing them with marquee?Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEWithout the legacy option the skylights are always projected: their 2d scripts don’t run in this situation. You need to create a proper model for the projection – this model can be different than the “normal” 3D model.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SETony,
I can not help based on this report, it is not a “known and corrected” issue from the past. To help I’ll need the complete workflow what you have done, all the commands in the order you started them and the original files – which can be gsm or xml files.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SENow we corrected the empty name error too, so you can drag these solo objects to ARCHICAD, and do not need to rename them. Thanks for your patience, and thanks for the reports.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SETony,
I attached a corrected file, compressed in zip.
On windows: you can easily replace the LP_XML.xsd file in Tool/WIN folder with the corrected one. This should solve the problem.
On mac: the converter is originally in a compressed file, which is unzipped when you first start the “MakeLibrary.pl” script in Sources/ArchiCADLibrary/Make. After that, you can replace the LP_XML.xsd in Tool/OSX/MakeGDLLib_X86/LP_XMLConverter.app/Contents/Resources with the downloaded one.
I hope it helps.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHi,
I downloaded the object and tried it many times with all the hotspots and different zooms but could not reproduce this issue. Did it happen on windows or mac or both? Which main versions and builds did you try?
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SETony,
Which LP_XMLConverter did you use? Is it from an ARCHICAD or from the LibDevToolKit? Mac or Windows? Which main version and build?
There was buggy LP_XML.xsd file earlier, if you know where to find it, you should add a new line under the ContPen tag (somewhere around line 470…):
<xs:element name="ContVis" type="BooleanYesNo" />I can help you where to find that, or send you a proper file if you answer my questions above.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThere is no function in GDL for checking if parameter changes are made with multiple selection. In this situation the modifications are always made on the last selected elements, and the changes are pushed to the other selected elements parameterlist. Locking or setting the unique flag for parameters does not affect this workflow.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEKeeping the name does not resolve the problem with migration. Called macros are stored with their ids, so they won’t work with changed elements until you resave them. I suggest to always use the source format of the libraries where you can easily search for callers of a macro.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThere will be failures in case of library updates or migrating to new versions – when parametrization of a libpart can change. Pla saving can be wrong too – you won’t be able to use your pla in an upcoming version if the called library part is migrated.
If you need one of our placeable library parts as a macro, then you should open it with the editor and save as a macro (not placeable) with a new name. Then you can use it in your libraries.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE
