Custom WD Marker and IS

[Anonymous]

I created a new wd marker to show something(not the WD ID) on floor plan. The marker text string is "C0918" or "FM1024" end etc.

the rules are:
1) prefix string + dimension string

2) prefix string tell people the opening type (door or window), opening method(Sliding or others) or special usage(Fire Protection door and etc.).

3)dimension string = the first two characters of width + the first two characters of height.

for example, if I want to marker is fire protection door (1500mm width, 2400 mm height), the marker string is: FM1524

OK. I think it is enough.

I did it, and everything is perfect on floor plan.

then, in IS setting, I use MARKER TEXT instead of WD ID.

then, problems come. when the IS is created, Marker Text is strange. It seems that the subroutine of calculate marker text is skipped. Marker text in schedule is keep the original data.

i can not find any document about global GDL parameters of ArchiCAD v8.1.

Who can help me?

[Karl Ottenstein]

The I.S. should have no problem displaying the value of any custom parameter of your object.

I'm wondering: when you careate your special marker string, do you use the PARAMETER statement to store that value in a text parameter? And, then, in the I.S., did you click on "Additional Parameters" in the Fields tab, and locate that special text parameter and use it in your schedule?

If you did these things, then I'm not sure what the problem would be.

Karl

PS GDL manual is a PDF file with 8.1, or the current manual is online at graphisoft.com under Support / Documentation.

[Anonymous]

Sure. I put it in AC_MarkerText_1.

the routine is :

init -> calculate length data -> convert to text -> add prefix and postfix -> put string into AC_MarkerText_1 -> TEXT2 x, y, AC_MarkerText_1


The picture is my IS setting. I use Marker Text, not ID.

I test Standard WD Marker (Windows - Door Marker - 70, installed by ArchiCAD) with the setting, all door/ window Marker Text is "Custom". But mine Marker is calculated string, only wrong result.

[Anonymous]

Sorry, I foget to attach picture.

[Anonymous]

May be it is a bug. Because I put a default value into AC_MARKERTEXT_1. When I create the schedule first time, the marker text in the scedule is the default value. So I think when create a schedule, ArchiCAD do not call all marker object to get new markertext. AC use a cached text instead.

And here is another possibility. I use AC_MARKERTEXT_1 with wrong method.

I beg for a completed global variable manual. But where is it? Should I pay for it?

[Karl Ottenstein]

Wolf wrote:
May be it is a bug. Because I put a default value into AC_MARKERTEXT_1. When I create the schedule first time, the marker text in the scedule is the default value. So I think when create a schedule, ArchiCAD do not call all marker object to get new markertext.

I just verified the behavior that you have seen. Neither a Rebuild nor a Rebuild/Regenerate would update the custom text - so the code in the door marker was not being called. Opening the object settings dialog for the door object and closing it, or changing the door width/height in the Info Box caused the code to run and the marker text to update.

I don't know offhand how to make the code run at 'rebuild' time. Perhaps someone else does?

Karl

[Anonymous]

Thanks Karl.

I think it is a serious bug, isn't it?

May gs should do something.

[Karl Ottenstein]

Wolf wrote:
Thanks Karl.

I think it is a serious bug, isn't it?

You're welcome. But, I'm not sure if it is a bug, or if you and I are doing something wrong. This is the first time I have played with modifying the code for a marker. Others here have a lot of experience doing this, and they may know the secret to make this work. Let's see if someone posts some suggestions this week.

[Anonymous]

Let me think...

Mmm, WD Marker Parameters or how it works is important to me now.

Thanks Karl, and I try to revole some parameters myself. If it is too difficult, I will post it here and ask for you.

Thanks again.

[Anonymous]

I haven't had the time to test your specific example, but I have had some similar experiences with elevation markers. I suspect that this is a bug and is seriously in need of fixing. At least it is remedied by opening and closing the settings window and doesn't require reloading the libraries (which has happened to me in the past).