topic Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm) in GDL

Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Sun, 30 Apr 2023 01:48:48 GMT

Hi All

I have created a label that extracts data from Walls. When placed, it is positioned parallel to the Wall. I have used a Request statement to get the width of the relevant data text to create a 'pill-shaped' frame (incl. fill). This label also has a custom leader that points to the element (Archicad's Pointer is not used). This is all working well. What I would like to do (something I'm struggling with and seeking help on) is to be able to dynamically move the 'pill-shaped' frame to three different fixed positions along a single axis (parallel with the Wall). I have already coded a dynamic hotspot to run along this axis, and the 'pill-shaped' frame runs along with no problem, but it is infinite. I want it to be fixed to three positions. Refer to the attached image for where I would like the positions fixed. From my exploration and testing, I can't get the text width into the Parameter script (where I'm trying to fix these positions with a Value statement). FYI my Value statement looks like VALUES "dynamicOffset1m" RANGE [-0.0015,0.0015] STEP 0, 0.0015. I'd like to replace the '0.0015' with text width calculations. Does anyone know how to achieve this? Thanks in advance!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Barry Kelly — Wed, 03 May 2023 06:17:51 GMT

Just off the top of my head without testing, wouldn't you just use the width value you got from the REQUEST?

i.e the same parameter/value you use to set the text box width.

Assuming the returned parameter is 'box_wid'

Something like ...

VALUES "dynamicOffset1m" -box_wid*0.5, 0, box_wid*0.5

I wouldn't use STEP, just give the 3 values you want to use.

Barry.

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Mon, 01 May 2023 02:34:14 GMT

Hi Barry

You would think that is the obvious solution! Although, unfortunately you can't get the 'box_wid' value as it is REQUESTed (and transformed with GLOB_SCALE) in the 2D Script. I have tried moving the REQUEST statement to the Parameter Script, but you get a 'Project dependent request' error.

Thanks

Brendon

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Lingwisyer — Mon, 01 May 2023 04:34:36 GMT

Since you are just having it snap to the sides, and each label maybe different, why not just have it be:

VALUES{2} dynamicOffset1mfg -1, Left, 0, None, 1, Right

Since the positions are set to nodes on the pill, the actual offset is kind of irrelivant to the user. Then in your script you just have a transformation which is dynamicOffset1mfg * box_wid.

Ling.

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Kevin Lee — Wed, 03 May 2023 06:18:25 GMT

Hi BR,

Yes! I always wanted to use the text string width for moveable hotspots but couldn't work out how.. as a workaround.. I'm using the custom leader to toggle between 3 anchor points.

DEFINE STYLE "tzg_marker1" LABEL_FONT_NAME, LABEL_TEXT_SIZE, ANCHOR, LABEL_FONT_STYLE

(Anchor set to 7, 8, or 9)

Let me know if you find a way to limit the hotspot points based on return values!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Mon, 01 May 2023 04:40:00 GMT

Hi Ling

That is in fact my fall back. But unfortunately this is not so great, as the 'text box width' will vary due to the called Wall data and scale of the View! Maybe I have encountered a limitation!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Mon, 01 May 2023 04:42:46 GMT

Hi Kev!

Yes this is an option too. Maybe it is a limitation! How good would it be to have a fix though!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Mon, 01 May 2023 04:49:29 GMT

Hi Kev

Upon having a closer look, I think there is definitely something in your suggestion worth exploring... I think I can move the frame the required distance no matter how long the length of text using this method. Now if I can only get a dynamic hotspot to link to the 'Anchor'... I'll give this a go and let you know! Thanks!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Jochen Suehlo — Mon, 01 May 2023 11:21:53 GMT

I attach an example from a stretchable cabinet.

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Mon, 01 May 2023 12:23:47 GMT

Thanks Joachim - much appreciated. Unfortunately, these fixed points are not tied to an output scale (e.g. 5mm at 1:100, or 15mm at 1:50). What makes my request even more complicated is I'm trying to tie my fixed points to a length that will vary depending on the width of the RICHTEXT block.

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Piotr Dobrowolski — Tue, 02 May 2023 08:46:02 GMT

Refer to window / door marker objects to see how it works:

HOTSPOT2 x, y [, unID [, paramReference [, flags [, displayParam [, "customDescription"]]]]]

the key is "displayparam"

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Tue, 02 May 2023 23:01:17 GMT

Hi Piotr

Yes, thanks. I do have a Hotspot2 command that utilises displayParam (referring to my image you can see it is called 'Display Offset mm'). Unless I am missing something, the problem is I can't fix that parameter to a RANGE because those values are not accessible in the Parameter script. I'll take a closer look in any case. Thanks again - appreciate your response!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Piotr Dobrowolski — Wed, 03 May 2023 06:19:06 GMT

You have to have the both parameters set and "valued" in parameters script.

That is another trick, and 1024 status is another

Actually I dig some example where there are 3 parameters: the M (meters) MM (millimeters) are real number. But I believe I have some other with just 2 parameters.

hotspot2 0, 0, unID, extensionLineLengthM, 1+1024, extensionLineLengthMM :unID = unID + 1 !BASE (hidden) hotspot2 0, 1, unID, extensionLineLengthM, 3+1024, extensionLineLengthMM :unID = unID + 1 !REFERENCE hotspot2 0, -extensionLineLength, unID, extensionLineLengthM, 2+1024, extensionLineLengthMM :unID = unID + 1 !MOVING

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

ShaunTaylor — Wed, 03 May 2023 05:29:09 GMT

Hey Brendon,

I am not sure this can be achieved if your label is sizing based on scale (paper size). Assuming you need to right a "Values "pointPosition" range(..." command in the parameters script. If your label is sizing based on scale, then you can't calculate the range because there is no way of requesting scale in the parameter script.

I got close by creating a style in the master script, then by using "stw(myString)". But unfortunately, that doesn't factor in the scale. So, the number I get is only correct using model size and not paper size.

I know Graphisoft removed using "glob_scale" in the parameters script in version 20. It would be good if they can give us an alternative to requesting scale from the model.

Cheers,

Shaun.

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Peter Baksa — Wed, 03 May 2023 09:48:18 GMT

I know Graphisoft removed using "glob_scale" in the parameters script in version 20. It would be good if they can give us an alternative to requesting scale from the model.

It was removed because using it would lead to incorrect state of the object.

Anything in Archicad can have multiple views with different settings, but only one parameter set. Scheduling, teamwork and interoperability features use the parameter set, it can't depend on the last applied view with the BIM approach.

A workaround is to give graphical feedback in GLOB_FEEDBACK_MODE. Then the hotspot doesn't have to have a limit, but you still can give hint about the separate options. An editable hotspot can be drawn at a fixed position x: hotspot2 x, 0, unID, editedParam...

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Wed, 03 May 2023 13:12:14 GMT

Thanks Peter - I knew you would have something to share! And thanks everyone for your comments, they are all much appreciated! While I don't have a perfect solution ('by design' for a good reason), I think Peter's use of GLOB_FEEDBACK_MODE (which I never used before) and having fixed hotspots (which can be driven by the text width are great in combination. Refer to attached image. It would be great if Hotspots could be seen only when GLOB_FEEDBACK_MODE = 1 though (unless of course I am missing something)!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

ShaunTaylor — Thu, 04 May 2023 00:00:25 GMT

Hi Brendon,

I think I have managed to come up with a solution thanks to Peter's comment. Peter gave me an idea which seemed to have worked. Although I didn't use GLOB_FEEDBACK_MODE, I used a variable in the 2D Script that forces the hotspots to not exceed the beginning of your curve via an if statement. I have attached the file.

Cheers,

Shaun.

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

Brendon Reid — Thu, 04 May 2023 01:09:20 GMT

Hi Shaun

Although my Label works the opposite (my 'pill' moves, not the leader), the functionality provides an even better result! And such a simple way to do it! Thanks for this; much appreciated!

Re: Limiting 2D Symbol dynamic hotspots to a (Value) Range of output units (mm)

David Shorter — Thu, 04 May 2023 07:09:12 GMT

Hi Brendon

Doing in the label seems tricky so I made a new label and called the code label as shown in the script.

it needs a directional rotation (for the wall direction) and a moveable hotspot but that shouldn't be difficult.

Just a thought.....

Hope this helps