Forum General discussions About this site Problems and solutions in GDL Forum rules and functions

[Gergely Fehér]

This request can not be used in parameter script, check it in the documentation please: “Expression returns 0 and contains dummy return values (emtpy string or 0) if used in parameter script, causing additional warning.”

Instead of this, you can use it in the ui script, and use the returned values in a custom popup infield, as it is written here: https://gdl.graphisoft.com/tips-and-tricks/display-properties-with-labels/

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Thanks for the report, I’ll add this issue to our bug database, and we will check the possibilities.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

I’m afraid it is not possible with only GDL programming. You can create an addon, which reads data from zone and stamp, and creates new objects based on that, or as a workaround you can put a slab into each zone, and use the slab accessory.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Dynamic arrays can be returned, but it will be converted to a single array. If we need to return data in this way, we usually return the sizes of the array first, the the array itself:
end arraySize1, arraySize2, array

After that in the caller object you can rebuild the original array in a nested loop.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

You should not use macro calls with variable macro names – as it kills background processing. Thats why we won’t enable variable names in the pointcloud command in the near future.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

ROOM_VOLUME parameter always stores the gross volume of the zone, before the subtractions. For the first check, it seems the net volume is not available from GDL scripts.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

By the way, this thread should be somewhere under “Problems and solutions in GDL”, not in “General discussion”.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Try it with the following paramscript, where “size1” and “size2” are the array size parameters and “myArray” is the array with changeable size:

values "size1" range [1,)
values "size2" range [1,)
 
 
if GLOB_MODPAR_NAME = "size1" or GLOB_MODPAR_NAME = "size2" then
                dim _tempArray [][]
                _tempArray = myArray
 
                dim myArray [][]
                for ii = 1 to size1
                                for jj = 1 to size2
                                                if ii > vardim1(_tempArray) or jj > vardim2 (_tempArray) then
                                                                _value = 0
                                                else
                                                                _value = _tempArray[ii][jj]
                                                endif
                                                myArray[ii][jj] = _value
                                next jj
                next ii
                parameters myArray = myArray
endif

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Please attach a sample library part – without that we can not check what’s wrong…

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Requests about properties only work with labels – as it is written in the documentation. (And zone stamps as they are working like labels). Properties should not take any effect on the 2d display (and 3d model) of any objects – except the visual override option outside GDL.
Everything which changes the symbol or model must be the library parts parameter – properties are just additional things attached to the element to store information about the library part.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Joachim,
As I know there is no additional documentation for that… It is allowed to use your own parameters, so you can use the paramscript to make calculations and then use the calculated value in that short field. Variables can not be used for that purpose, you can only use the objecst own parameters and globals.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

It is stored in the addon’s internal database. It will be stored until ARCHICAD runs and the addon exists. If you restart ARCHICAD, the addon will ask again for the folder. It is not available in GDL scripts, so you can not store it in parameter in this case.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

It can not be stored as a paramvalue. You can create lists, where there are 3 columns for these information. In GDL, you can reach this data only in 2D/3D – so you can display it.

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

Hi Francois,
I checked the object and it has errors in it’s 3D script – there are invalid poligons in it. I would like to have more informations about these elements, so please contact us at gdlcenter@graphisoft.com

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Gergely Fehér]

“Full_ID_of_parent” is not available to use in parameter script. It is a 2d only functionality, to be able to display it in 2d, so it is not a bug, it is the planned functionality. Please check Requests in GDL Manual: https://gdl.graphisoft.com/reference-guide/request-options/

Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE

[Author]

Posts