topic Re: Possible to use element property value in a label? in GDL

Possible to use element property value in a label?

Mats_Knutsson — Thu, 19 Jan 2023 09:29:34 GMT

Hi,

I'd like to create a label with a 2D geometry, say a circle that changes color according to the value (text content) of a certain property. Is this possible? Let's say I've created a property "LENNART" available for doors. The property is an option set with values A, B and C and the label should change colour depending on the property value... A=red, B=green etc.

/Mats

Re: Possible to use element property value in a label?

runxel — Thu, 19 Jan 2023 10:25:50 GMT

In short: it does not work. A GO rule can't catch the label – since it does not have the property.

And the GDL label itself can not be stylyed either, since it can't read the property (it only gets a GUID as reference pointer).

It's mad. Probably GS themself has no clue what the endgame here is.

But the idea is brilliant, and I know someone who scripted a door for their office having this feature built in. Then the GO kicks in and styles the circle.

Re: Possible to use element property value in a label?

Lee Hankins — Thu, 19 Jan 2023 11:59:25 GMT

We have set up a Graphic Override which searches for a Property assigned to Doors to determine if the door is Existing, New Leaf in Existing Opening, New Doorset in existing opening and New Door. The graphic override then changes the colours of the doors themselves to match a pre-defined Key so we generate a Door Key Plan.

Re: Possible to use element property value in a label?

Mats_Knutsson — Thu, 19 Jan 2023 14:34:09 GMT

It's not what I'm after. It's up to 6 different properties (= 6 colored blobs in a 2x3 matrix)...

Re: Possible to use element property value in a label?

SenecaDesignLLC — Thu, 19 Jan 2023 14:41:06 GMT

Not currently possible with our a python script.

You can use the id of the door to change both a label and the door object and property

Re: Possible to use element property value in a label?

poco2013 — Thu, 19 Jan 2023 19:26:41 GMT

Just to clarify for those interested in how a Python script works in Archicad and why it is so limited. it is possible, but I think you would agree that the configuration is more trouble than worth in this instance.

The problem, as said, is that labels are 2D elements and 2D elements can not contain properties. The work around is to simply create a object which is simply a circle with a fill. Then classify it and add the option property. You would need to add a second property tying it to a door ID and perhaps a third property identifying the object as a door identifier -- or maybe just use the classification.

The Python script would read the door criteria (whatever) and the associated symbol ID and then set the symbol option accordingly. A graphic override (one for each option) would then set the colors according to the option value.

IOW -- just set the door id accordingly -- or modify the door gsm to include a color identifier and good luck with that?.

Re: Possible to use element property value in a label?

Barry Kelly — Fri, 20 Jan 2023 01:16:33 GMT

@poco2013 wrote:

The problem, as said, is that labels are 2D elements and 2D elements can not contain properties.

The label does not need to contain the property.

It reads the property from the object, which can be done.

The label can read and display the property with no problems.

The question is can the label read the value of the property and act on it.

If property value = A then change the label colour to red.

If property value = B then change the label colour to blue.

Without setting it all up, off the top of my head I can't remember if the label can utilise the value of a property or as runxel said it can only read and display the property.

No time to investigate right at the moment.

But if I get a chance later I will have a look.

Barry.

Re: Possible to use element property value in a label?

poco2013 — Fri, 20 Jan 2023 01:55:09 GMT

@Barry Kelly wrote:
The question is can the label read the value of the property and act on it.

To my knowledge, OOTB Archicad labels do not feature any custom actions, other than programed. I presume you are suggesting writing a custom gsm label. Than I would agree that it would be possible since associated labels contain a parent GUID field or you could use the parent ID field if it was unique. This would not be possible with a Python script since it can not, at present, address the label type.

Of course, this could be easily done with a C++ AddOn but i don't think anyone wants to go there.

Re: Possible to use element property value in a label?

Palawat — Fri, 20 Jan 2023 11:25:44 GMT

Yes, a GDL label can do that.

In general, you can request PROPERTIES_OF_PARENT and then populate them using UI_CUSTOM_POPUP_INFIELD, in the UI scrip, to a parameter (a string type). Then assign it to "LENNART" by using the "Parameters" tab/page on GDL editing window, or by using the UI.

in 2D script, you then request PROPERTY_VALUE_OF_PARENT and use the value like;

if value = "A" then

...set your backgroud fill/pen

endif

There might be more requests needed. This is just from the top of my head. Sorry if I missed anything. But the thing is, if a built-in Properties Label exists, then label can definitely get that data.

Re: Possible to use element property value in a label?

Mats_Knutsson — Fri, 20 Jan 2023 12:58:15 GMT

This would make a perfect tutorial case for custom gdl label scripting :). I don't know how to do this...

Re: Possible to use element property value in a label?

SenecaDesignLLC — Fri, 20 Jan 2023 14:15:52 GMT

Pm me I have a label that already reads properties.

Re: Possible to use element property value in a label?

Palawat — Sat, 21 Jan 2023 04:48:12 GMT

This is not a tutorial but it should help.

First, you need a parameter (a string type) to act as an "id" (as in GDL Ref. Guide for PROPERTY_VALUE_OF_PARENT). Let's call it "criteriaProp".

*The "gs_ui_current_page" is there for the UI script to work. If you don't have it already, please create it too.

UI script;

ui_dialog "Test Label" dim pageTitle[1] pageTitle[1] = "Custom Settings" dim pageIcon[1] pageIcon[1] = "" dim pageID[1] pageID[1] = 1 ui_current_page gs_ui_current_page ui_page gs_ui_current_page ! Page 1 -------------------------------------------------------------------------------- ui_page 1, -1, pageTitle[1], pageIcon[1] dim parentProperties[] n = request ("Properties_Of_Parent", "", parentProperties) n = request ("Property_Name", criteriaProp, typeName, groupName, propertyName) ui_custom_popup_infield "criteriaProp", 10, 20, 200, 20, 1, 3, 2, propertyName, "None", "", "", "None", parentProperties

Here, we populate the requested "parentProperties" into "criteriaProp" so you can select which property to use as a criteria.

The requested "propertyName" is there so the UI show the title instead of "id" after a property is selected. (Within the ui_custom_popup_infield .... , try and replace it with "" and see what happen after selecting the property in UI).

The "None", ... is there in case there is no supported property, just in case...really. You can also set the parameter to "None" as default if you want to.

2D script;

! Getting value --------------------------------------------- taggedValue = "" dim propertyValues[][] dim1 = 0 dim2 = 0 type = 1 n = request ("Property_Value_Of_Parent", criteriaProp, type, dim1, dim2, propertyValues) if n & (glob_elem_type = 3 | glob_elem_type = 4) then ! Label works on D/W only. if type = 4 then ! String taggedValue = propertyValues[1][1] else text2 0, 0, "The criteria selected is not supported" endif else text2 0, 0, "The Element/Property selected is not supported." endif ! Start doing your thing ------------------------------------ text2 0, 0, taggedValue ! Just to check the value. Comment this out or delete it later. if taggedValue <> "" then if taggedValue = "A" then ! set your background fill/pen endif if taggedValue = "B" then ! set your background fill/pen endif !....... endif

Now we request PROPERTY_VALUE_OF_PARENT which return the value via propertyValues (2 dimensional array). In this case, we know for sure that dim1 = 0, dim2 = 0 since we create the property "LENNART" ourselves. So there's no need to fuzzing around dim1 and dim2. The value we want is propertyValues[1][1]. Just assign it to a variable "taggedValue" then manage from there. (Note: You don't really need the "taggedValue", but it is a lot nicer than using propertyValues[1][1] every time.)

You can also disregard the glob_elem_type thing if you don't want to limit the label to be used only with D/W.

Have fun scripting 🙂