Custom text in window markers

[Barry Kelly]

With AC 8.1 (R2) is it possible to have custom text appear in the window marker based on a parameter set in the window settings - not the marker settings?

I can add a parameter to the marker that will give me custom text - but I don't want to do that.
I want to be able to set a window parameter and have the marker detect it and add in the text automatically.

For example.
I have a window that needs to be obscure glazed.
I want the note "OBS" to show in the marker on the floor plan.
Now I can add the note as a parameter in the marker easily enough but I don't want to do that.
I have a parameter in my window already that allows me to choose "OBS" glass and it changes the the material of my glass for me so my elevations and 3D look correct.
Can the marker detect the setting of the window parameter and adjust itself automatically?
I don't want to have to make the choice in two separate areas - obviously to eliminate errors.

In version 7.0 this was easily done as the marker text was a routine called into the window and therefore I could pass on the parameters.
Now in 8.0 if I want to use the marker it seems I can not do this.
Of course I could still use the call routine but then I can not turn the marker on or off as it is not really a marker.

In 7.0 we have an "if WIDO_CUSTOM_MARKER<>0 then....." call the text routine.
This allowed us to turn the text on or of with the display options > doors & windows > show with dims
In 8.0 the WIDO_CUSTOM_MARKER variable always seems to be equal to zero no matter what the settings.
Is this now defunct as the markers can be turned on or off individually from the windows?

Can anyone tell me if it is possible (to pass the custom text to the marker), and if so, how?

Thanks for any help you may be able to give.

Attached is a quick screen shot to show what I want.

[Anonymous]

Most door & window standard parameters are available as globals. Try using them in the label object. The parameter WIDO_MARKER_TEXT might do the trick. There is also WIDO_PREFIX, etc... And a Request(ID_of_Main...) might work as well.

[Barry Kelly]

Thanks for the reply Matthew,

Matthew wrote:
Most door & window standard parameters are available as globals. Try using them in the label object. The parameter WIDO_MARKER_TEXT might do the trick. There is also WIDO_PREFIX, etc... And a Request(ID_of_Main...) might work as well.

I found another variable - REQUEST("window_door_show_dim", "", show) that gives me the display option setting of on or off.
This means I can keep the call function in my window script and can turn it on or off on a global basis.

In V7.0 we use - WIDO_CUSTOM_MARKER, which is the dimension on or off button in the window settings (see attachment).
This allows us to turn the text off on a window by window basis.

The wierd thing is, this always seems to have a value of 0, no matter what the setting for the dimension button.

The statement - "if WIDO_CUSTOM_MARKER<>0 then....." call the text macro - works fine toggling the text on or off with the button.
If I simply say - PRINT WIDO_CUSTOM_MARKER in the 2D script, all I get is "0" whether the button is on or off.
So why does the above statement work?
Is there another way of finding and listing it's real value?

But V8.1 doesn't have the same on/off button as V7.0.
Is simply choosing "NO MARKER" from the dimension marker settings the same thing?
It doesn't seem to have any effect in the script now at all.

Why couldn't V8.0 have been left with a simple marker on/off button?
If on then choose the marker you want.

Frustrated but getting closer to what I want.
Barry.

P.S. An even wierder thing is if I copy and paste a wall with a window from V7.0 into V8.1, the window has automatically a "CUSTOM MARKER - V70" as a standard marker. This then shows all the info I need and behaves as I want (as it used to in V7.0). It seems to be treating the called macro as a marker.
If I alt-click the window and insert exactly the same window in another wall - no custom marker.
It is still reading exactly the same script - so what's the difference?

[Anonymous]

Yes these thing can be a bit of a brain tease.

There are still some advantages to writing the tags into the door & window scripts themselves (easier to control their behavior) but it requires that you create or modify all the door & window that you need. I have switched to assigning the tags in the new way so we can use any door or window without having to make the modifications (for which I haven't the time).

I recommend you try to crack the separate (assigned) label approach. It will ultimately be the easiest to maintain.

[David Maudlin]

Barry:

It has been awhile since I went through this same problem (updating my libraries for the change from ArchiCAD 7 to 8 ), so my recollection is a bit fuzzy, but I do recall looking for (and not finding) the Custom Window Marker button in 8. I was not trying to pass additional parameters (only the ID) to the marker, so I eventually wrote my own marker (which can be used by any door or window). I don't know how to pass any custom parameter from the door or window to the marker, so I think you need to stay just in the window or door part. You could add a new Boolean parameter to the window or door that replaces the Custom Window Marker button (this parameter could be added to all your doors and windows using you own Subtype), and then write in the 2D Script the code to show the text you want. You should be able to use
"Window_Door_Show_Dim" so this can be hidden by the Display Options.

HTH

David

[Barry Kelly]

Thanks Matthew and David,
For now I have decided to keep the script within the window part itself.
I have simply swapped it to use "Window_Door_Show_Dim", which allows me to turn all the tags off globally via the display options.
I have also added a parameter that allows me to turn the tags off individually from within the window parameters.
I'll keep playing with the markers though and if I have any joy i will post back.
Thanks again,
Barry.