topic Re: Hack the Surface Label in GDL

Hack the Surface Label

RHF55 — Tue, 24 Sep 2024 08:10:32 GMT

I would like to edit the Surface Label 25 to show the text of a surface before a delimiter. For example:

Surface Name is TC:Timber Cladding

Label to shown only TC

This is the code I have used to get this working on a wall label i wrote a while ago:

!======split len = STRLEN (string) iDotPos = STRSTR (string, sep)!sep is the seperator code = STRSUB (string, 1, iDotPos - 1) mat = STRSUB (string, iDotPos+1, len-iDotPos)!material if display_txt = 'code' and code<>"" then string=code endif if display_txt = 'mat' then string=mat endif

But I cant figure out where to catch the surface name and split it in this object. I think it might be happening in the macro label_content_macro. Any wizards out there that can figure this out??? @Barry Kelly ?

Of course this would not be required if GS would give us an ID field for surfaces the same as building materials.

Operating system used: Mac Intel-based 12

Re: Hack the Surface Label

AllanP — Wed, 07 Aug 2024 03:56:00 GMT

Yes, that is the correct place where the suface is gathered from.

from gdl

(they are just using a parameter with SURFACE_ in front of the desired gdl code in this list...

from the macro

which then gets the id of the surface

_iAvailableMaterialContent

that then convert's into a name

_nameSurface

which gets assigned to:

_sSegmentLocal

which gets assigned to

_sSegmentGlobal

which gets assigned to

sRowsOfLabel

which gets assigned to

tempsRowsOfLabel

Which gets returned from the macro using the "end returned_parameters" command...

I love the way Graphisoft make this easy to find...

P.S.

it looks like the typed prefex is in array point 1

and the material is in array point 5

using the following in a copy of the surface label

text2 0,1,_sContentStringsHead[1][1]
text2 0,2,_sContentStringsHead[1][5]

Re: Hack the Surface Label

Barry Kelly — Wed, 07 Aug 2024 03:22:13 GMT

Having a quick look at that surface label, it seems it calls a subroutine to "collect_content".

This returns the information for the surface that is stored in the parameter array ... _sContentStringsHead

So I am assuming you would need to perform your SPLIT routine on that parameter value to get the part of the name that you want.

There are 2 GOSUBs in the label, one to get the information and one to display it.

Your split routine needs to be done between those two GOSUBs.

The thing is that _sContentStringsHead parameter is an array, so you will have to figure out what part of that array the information is in for the surface name.

You then need to SPLIT that name and then replace it back in the array so it is then used in the 'position_and_draw_label' sub-routine.

At the moment I don't have the time to investigate further.

But hopefully that will give you a start.

Barry.

Re: Hack the Surface Label

RHF55 — Wed, 07 Aug 2024 03:36:05 GMT

Well I dont feel so silly not being able to trace that, now Ive seen how serpentine the structure is. Thankyou for your detective work @AllanP

Re: Hack the Surface Label

RHF55 — Wed, 07 Aug 2024 03:44:25 GMT

I will give this a shot @Barry Kelly, thanks for your time looking into this. I'll post the hacked label if I'm able to get it to work.

Re: Hack the Surface Label

RHF55 — Wed, 14 Aug 2024 22:46:41 GMT

Thanks for your PS @AllanP

I got it to work with this. It will be a very useful label now 🙂

I just need to

! ============================================================================== "collect_content": ! ------------------------------------------------------------------------------ ! ============================================================================== nTrans = 0 _nRowLabel = 0 dim _sRowsOfLabel[][] _sRowsOfLabel[1][1] = "" dim _sContentStringsHead[][] _sContentStringsHead[1][1] = "" gosub "call_general_label_macro"! returned text array, _nRowLabel, _sRowsOfLabel _sContentStringsHead = _sRowsOfLabel !split surface to code string = _sContentStringsHead[1][5] iDotPos = STRSTR (string, ":") code = STRSUB (string, 1, iDotPos - 1) _sContentStringsHead[1][5] = code return

include an IF statement to check if there is a ":" in there and it will be good to go!

Re: Hack the Surface Label

RHF55 — Wed, 14 Aug 2024 22:47:44 GMT

Im struggling with the CONTAINS syntax, this is returning an error that "missing THEN statement". Driving me nuts!

! ============================================================================== "collect_content": ! ------------------------------------------------------------------------------ ! ============================================================================== nTrans = 0 _nRowLabel = 0 dim _sRowsOfLabel[][] _sRowsOfLabel[1][1] = "" dim _sContentStringsHead[][] _sContentStringsHead[1][1] = "" gosub "call_general_label_macro"! returned text array, _nRowLabel, _sRowsOfLabel _sContentStringsHead = _sRowsOfLabel !split surface to code IF CONTAINS (sep,_sContentStringsHead[1][5]) THEN string = _sContentStringsHead[1][5] iDotPos = STRSTR (string, sep) code = STRSUB (string, 1, iDotPos - 1) _sContentStringsHead[1][5] = code ENDIF return

Re: Hack the Surface Label

AllanP — Thu, 08 Aug 2024 02:55:19 GMT

i cant find the "CONTAINS " command in the GDL manual

if you use:

if STRSTR(_sContentStringsHead[1][5]),sep) > 0 then

!!!BODY HERE

endif

Re: Hack the Surface Label

Barry Kelly — Thu, 08 Aug 2024 02:59:21 GMT

There is no CONTAINS command in GDL (that I am aware of).

STRSTR is what you need to determine if a character is a part of a string.

Barry.

Re: Hack the Surface Label

RHF55 — Thu, 08 Aug 2024 03:03:38 GMT

found CONTAINS here https://helpcenter.graphisoft.com/user-guide/137394/

will give STRSTR a try. thanks guys

Re: Hack the Surface Label

Barry Kelly — Thu, 08 Aug 2024 03:33:20 GMT

That is interesting.

It is the same format for the command, just STRSTR instead of CONTAINS.

I just checked the GDL reference PDF in 25 and it is STRSTR there.

I never noticed that in the Helpcentre website before (but I wouldn't have been looking for it specifically).

That website is actually out of date now and is no longer being maintained, just left as a reference I assume.

The Archicad help is now here on the Community but the GDL help is only found as a PDF in the application folder or the GDL Centre website here ... https://gdl.graphisoft.com/ (where it is also STRSTR).

Barry.

Re: Hack the Surface Label

RHF55 — Thu, 08 Aug 2024 05:21:15 GMT

Here is the hacked label if someone needs it. Pretty simple but very useful for us.

If you pimp it further, post back with your changes.

Thanks for your wizard help @AllanP & @Barry Kelly

Re: Hack the Surface Label

Lingwisyer — Tue, 31 Mar 2026 07:40:14 GMT

Anyone know if _sContentStringsHead contains bMat and / or bMat_ID?

ps. The Skin List Label uses the same macro structure so it would seem that it can. Just need to figure out how...

Re: Hack the Surface Label

Lingwisyer — Tue, 07 Apr 2026 08:11:15 GMT

I have gotten it to show bMat_ID, now I just need to figure out how to get it to only show the first/last ID for composites rather than the full contents list.

Re: Hack the Surface Label

Lingwisyer — Wed, 08 Apr 2026 09:06:50 GMT

The contents macro has an odd return when it comes to the BM of columns...

Maybe that is when the Skin List Label is not available for columns...

Ling.

ps. The BM_ID return seems to be empty in AC28+...

Re: Hack the Surface Label

Lingwisyer — Wed, 13 May 2026 08:46:05 GMT

Turns out that the Label Content Macro has a bug when it comes to surfaces...

If you flip a wall, the label inverts the inside and outside...

Ling.

Re: Hack the Surface Label

Benjamin Dani — Tue, 19 May 2026 14:08:42 GMT

Dear Ling,

Thank you for your feedback about Labels.

It seems like an incorrect behavior, however it would be great to know the exact settings you used and the environment you were able to experience this error.

I would like to ask you to create a ticket on our Support Site and describe the issue in detail, so our technical experts can investigate this further.

Thank you in advance!

Best regards,

Re: Hack the Surface Label

Lingwisyer — Wed, 20 May 2026 03:10:15 GMT

Looking more into it, it is less a bug, more an inconsistent behavior and UI issue. The macro pulls Wall_Mat_A and Wall_Mat_B which have an origin direction, which is relevant for doors and windows, and hence swap if a wall is flipped. I have detailed it in ticket #282137. I will see if the Wall_Flipped parameter can be used to make my BMat return consistent with the displayed surface. The macro UI is for GS to fix...

Ling.

Re: Hack the Surface Label

Barry Kelly — Wed, 20 May 2026 09:23:13 GMT

@Benjamin Dani

If this is the way we should be submitting support tickets, could we please have that page fixed so that it shows the ticket types as shown in the how to submit article.

Every time I have tried to use it, there is no "Product Support' Option.

I have even tried in a new browser and accepted "all cookies" and it is the same.

This is what I see ...

Barry.