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

[Joachim Sühlo]

And you can manually protect your whole object with a password in the GDL editor …

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

There are 2 ways: There was an old tool called “hidescripts.exe” but I don’t know if there are actual versions of it.
2nd: You can do it with the XML-Converter.

4.3 Hiding script sections: Library Parts provide a way to have the scripts hidden from the end user. This can be done in XML by adding 64 to the SectionFlags attribute of the script to be hidden. This will create a GSM file with the given scripts hidden. Converting a library part with hidden scripts back to XML will create empty script elements, so be sure to keep the original XML files after publishing the library.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Have you tried this (this REQUEST works in labels and markers to read Parameters from the associated objects):
REQUEST (“ASSOCLP_PARVALUE”, expr, name_or_index, type, flags, dim1, dim2, p_values)

Example from a GS-Marker:
! — Fire Rating ————————————————————–

if GS_iCustomText_5 = CTXT_MEASUREDVALUE or not(AC_show_firerating) then
firerating = “”
rrr = request (“ASSOCLP_PARVALUE”, “gs_list_firerating”,
index_firerating, type_firerating, flags_firerating,
dim1_firerating, dim2_firerating, firerating)
AC_MarkerText_5 = AC_FirePrefix + firerating ! Fire Rating Value
parameters AC_MarkerText_5 = AC_MarkerText_5
endif

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Thank You Péter,
your workaround works well.
But I found another solution:
AC_GLOB_ELEVATION works astonishingly in the marker and gives back the sill height of the window,
although this parameter is not created as paraneter in the window object (so ASSOCLP_PARVALUE does not work here).
If AC_GLOB_ELEVATION is as parameter in the marker, I can compare AC_GLOB_ELEVATION with AC_Sill_To_Curr_Story,
and if the 2nd one is bigger than the 1st one, I substract the story heigth of the sory below.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

I never dragged a picture; I always use copy and paste. That always worked well.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Try it with GLOB_FEEDBACK_MODE.
IF GLOB_FEEDBACK_MODE = 1 THEN
… Do not show the heavy parts
ENDIF

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Tank You Péter, perfect !

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

I got it, I had an logically error. Problem solved!

PEN foregroundPen
FILL myFill

PROJECT2{2} 3, 270, 3+32,
backgroundPen, xOrigo, yOrigo, fillDirect

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Thank You, Péter. That worked well with BOM.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Yes, UI_PICT with a 1 at the end instead of a 0.
Mask Value = 1
UI_PICT picture_reference, x, y [, width, height [, mask]]

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Peter, please check this:
If I create a new door object with subtype Door, I always get the sill’s tabpage.
If I choose a door subtype wit “GS” in the name, I will get no sill’s tabpage.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

If you convert the gsm file with the XML Converter Tool to xml, you can find the binary part of the preview picture.
It starts with the XML-Tag like this:
<Picture MIME=”image/png” SectVersion=”19″ SectionFlags=”0″ SubIdent=”0″ length_in_bytes=”9564″ platform=”Win”>
SubIndent = “0” is always used for the preview picture.
You can embedd more pictures into the object with use of the XML Converter Tool and use those pictures for example in the User Interface, but as far as I know you cannot change the selection of the preview to another of the embedded pictures.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

James, with your script the file is written into a special folder, which differs from Mac to Windows.
Maybe you did not find it (on Mac it is placed within the Library Folder). You could try to wrie the file in a special directory (use the keyword FULLPATH).
Some good examples of writing and raeding text files you can find in the GDL Cookbook 3, including the saving of parameter values.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

That is brilliant, it works perfectly! Thank you

Thanks to Frank Beister, who had published this on openegdl.org.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Joachim Sühlo]

Hi,
there a really a lot of differences, how the UI Elements are shown on Windows and MAC.
E.G. length and size of text, points of linebrakes, UI_Styles.

We use in our office the following REQUEST to distinguish between both platforms.

! Parameters for ArchiCAD version and Platform
Dose = 0
sts = REQUEST(“Name_of_program”, “”,TeX)
IF STRSTR(TeX,”.EXE”) OR STRSTR(TeX,”.exe”) THEN Dose = 1

And we always check the UI on both platforms.

GDL Object Developer
b-prisma
MAC OSx 10.14

[Author]

Posts