Forum Replies Created
-
Posts
-
How do I set up the script to use the Property Name as Value for a VALUES command in the new REQUEST (“Properties_Of_Parent) command (for a door marker)?
Following does not work:DIM _sTnCParamData[][5], _auswahl[], _parentProperties[] FOR i = 1 TO 5 _sTnCParamData[1][i] = "" NEXT i PROPERTY_FOLDER = 1 ! NEW: GROUP PROPERTY_ID = 2 ! NEW: ID PROPERTY_NAME = 3 ! NEW: NAME PROPERTY_VALUE = 4 ! NEW: VALUE PROPERTY_TYPE = 5 ! BRAND NEW TYPE n = REQUEST ("Properties_Of_Parent", "", _parentProperties) _numProperties = vardim1(_parentProperties) / 4 _sumParamNum = 1 for i = 1 to _numProperties _sTnCParamData[_sumParamNum][PROPERTY_FOLDER] = _parentProperties[4 * (i - 1) + 3] _sTnCParamData[_sumParamNum][PROPERTY_ID] = _parentProperties[4 * (i - 1) + 1] _sTnCParamData[_sumParamNum][PROPERTY_NAME] = _parentProperties[4 * (i - 1) + 4] _sTnCParamData[_sumParamNum][PROPERTY_VALUE] = "" _sTnCParamData[_sumParamNum][PROPERTY_TYPE] = _parentProperties[4 * (i - 1) + 2] _auswahl[_sumParamNum] = _sTnCParamData[_sumParamNum][PROPERTY_NAME] _sumParamNum = _sumParamNum + 1 next i VALUES "text_auswahl" _sTnCParamDataGDL Object Developer
b-prisma
MAC OSx 10.14Isn’t it the same method which is used by the old ADD-ON “Raumzubehör”?
Yes, about the Addon “Raumzubehör” = “Zone Accessory” I am talking.
There must be a switch to unlink the object from its Addon-Behavoiour.GDL Object Developer
b-prisma
MAC OSx 10.14BIMobject made such an object, but the script is encrypted.
This works both as accessorie part when placed, and as user defined polygon after placing, that cannot be updated by the zone accessorie.GDL Object Developer
b-prisma
MAC OSx 10.14Gergely,
are there any documentations about Parapet Wall Inset; this is not easy to understand and took me hours to figure out (I could not use GS standard because of an own rotation undo routine).
That there are only 253 Character allowed, is not helpful.
Is it allowed to use there variables defined in the Master-Script?
Is it allowed to use there Parameters set in the Parameter Script to shorten the total lenght?
E.G. ix = gs_frame_thk : PARAMETERS ix = ixGDL Object Developer
b-prisma
MAC OSx 10.14You mean something like this:
! — MVO: 3D Öffnungslinien an/aus
bOplinesTemp = 0
success = LIBRARYGLOBAL (“LibraryGlobals13”, “D_showBOpLine3D”, bOplinesTemp) ! Door
if success > 0 and bOplinesTemp <> 0 then
bOplines = bOplinesTemp
ENDIF! — MVO: Öffnungslinientyp 3D Öffnungsseite
success = LIBRARYGLOBAL (“LibraryGlobals13”, “gs_opline_type_m”, reqIOplineTypeTemp)
if success > 0 then
gs_opline_type_m = reqIOplineTypeTemp
endif! — MVO: Öffnungslinientyp 3D gegenüberliegende Seite
success = LIBRARYGLOBAL (“LibraryGlobals13”, “gs_opline_type_m_out”, reqIOplineTypeOutTemp)
if success > 0 then
gs_opline_type_m_out = reqIOplineTypeOutTemp
endif! — MVO: Öffnungslinientyp 3D für Nebentürblatt
success = LIBRARYGLOBAL (“LibraryGlobals13”, “D_iOpLineType2”, reqOplineType2)
if success > 0 then
iOplineType2 = reqOplineType2
endif! — MVO: Öffnungslinienstift 3D
success = LIBRARYGLOBAL (“LibraryGlobals13”, “D_opLinePen”, reqOplinePen)
if success > 0 then
gs_opLinePen = reqOplinePen
endifIF (bOverride_MVO_3D AND or_bOplines3d) OR (NOT(bOverride_MVO_3D) AND bOplines ) THEN
IF (bOverride_MVO_3D AND or_bOplines3d) THEN
temp_opLineType3dIn = or_iOpLineType3dIn
temp_opLineType3dOut = or_iOpLineType3dOut
gs_opLinePen = or_opLinePen
gs_opline_style_m = gs_opline_style_m
ENDIFIF (NOT(bOverride_MVO_3D) AND bOplines ) THEN
temp_opLineType3dIn = gs_opline_type_m – 1
temp_opLineType3dOut = gs_opline_type_m_out – 1
gs_opLinePen = gs_opLinePen
gs_opline_style_m = gs_opline_style_m
ENDIFENDIF
GDL Object Developer
b-prisma
MAC OSx 10.14Is it possible to create a separate 3D-Script for List calculation, like:
IF GLOB_SCRIPT_TYPE = 9 THEN?GDL Object Developer
b-prisma
MAC OSx 10.14ski_no = WALL_SKINS_NUMBER
And the REQUEST was not correctly copied (Array-Index) was missing:
x = REQUEST{2} ("Building_Material_info", wand_mat[ii], "gs_bmat_surface", mat_index[ii])
This seems to be prohibited by the forum software (square brackets where left out)GDL Object Developer
b-prisma
MAC OSx 10.14Normally you can write:
DIM _param_value[] _param_value[1] = 'opt1' _param_value[2] = 'opt2' _param_value[3] = 'opt3' _param_value[4] = 'opt4' _param_value[5] = 'opt5' _param_value[6] = 'opt6' VALUES "param1" _param_valueBut this does not work with VALUES{2}, I do not know why.
Instead this works, but I don’t know if this is what you wanted.DIM _param_val[] _param_val[1] = 1 _param_val[2] = 'opt1' _param_val[3] = 2 _param_val[4] = 'opt2' _param_val[5] = 3 _param_val[6] = 'opt3' VALUES{2} "param2" _param_val[1], _param_val[2], _param_val[3], _param_val[4], _param_val[5], _param_val[6]And you can loop it like this:
FOR i = 2 TO 3 VALUES{2} "param" + STR(i,1,0) _param_val[1], _param_val[2], _param_val[3], _param_val[4], _param_val[5], _param_val[6] NEXT iGDL Object Developer
b-prisma
MAC OSx 10.14Your Pictures size value of 136,80 should be half the size of the picture, as I think.
If I do this, the captured screenshot of the UI matches with the picture, in your script not.ui_x1 = 1 ui_y = 1 ui_selection_h = 100 UI_INFIELD{3} "sentry_type", ui_x1, ui_y, 160, ui_selection_h, 2, "Sayfa-SENTRY-Guardrail", 2, 1, 160, 100, 144, 80, sentry_concrete, type_sentry[sentry_concrete], type_sentry[sentry_concrete], sentry_metal, type_sentry[sentry_metal], type_sentry[sentry_metal]Although the edges are still jagged a bit, they are absolutely identical to the picture you loaded up.
GDL Object Developer
b-prisma
MAC OSx 10.14Please post your Script for the UI_INFIELD and the original size of the image.
GDL Object Developer
b-prisma
MAC OSx 10.14I think, the size in pixel of the image must be the same in the User Interface as in the original image file. You can measure this with a screen capture application. If it is to small, you must widen the Infields.
GDL Object Developer
b-prisma
MAC OSx 10.14Gergely,
a question about the running of the Parameters commands:
They are placed in the Master Script.
Does your answer mean, that the Parameters command is only executed,
if a parameter is changed, which applies to the Parameter Script as whole, although the command is placed in the Master Script?
As the Master Script is executed more often, does it skip the Lines with the Parameters Commands?GDL Object Developer
b-prisma
MAC OSx 10.14
