Window/ door Local standards for wido_orientation

[Anonymous]

I have created my own custom doors and windows and for some reason the wido_orientation global variable does not work in the scripting. In the gdl reference it says that it will only work with windows created to "local standards" what the heck is that??? please help as i am finding it very frustrating

I have print wido_orientation in my masterscript and when i open up the object it is prints blank. if i open the 3d window it prints L or R as required why does it not print L/R when i open up the window as this works with archicad default objects?

thanks
mark

[Anonymous]

I think what they mean by local standards is which way is considered right or left.

I don't understand what you mean by "printing" in the master script and 3D window. (I know programmers used to use "print to screen" or such, but for real world clarity I prefer to reserve the term "print" for putting stuff on paper.) To display text in 2D or 3D requires the Text2 or Text in their respective scripts. The master script is mainly for initializing or calculating variables that are used in multiple scripts - not for display or output.

You need to be a bit more specific in what you are trying to do. Sample code and pictures can be a big help.

[Anonymous]

sorry i did mean the "print" function for debugging rather than text commands. i want to have a parameter which contains a factory code based on the orientation of the window

facname=drtpe+fi+"SS"+wido_orientation+wid+len

drtpe= type of door (pvc / timber etc)
fi= finish of door ( ral colour
etc.

i want to have the orientation of the door/ window to be included so that the code is a complete description of the window

[Anonymous]

I just did a test and it works fine for placing the text in plan.

If you are trying to use the PARAMETERS function to set a user parameter value in the master script so that it can be read by the schedule then you may be out of luck. I have already run into this with the GLOB_POS_Y (etc.) parameter. It seems to be an execution order problem but the values of the globals cannot be used to force the values of user parameters.

[Frank Beister]

It seems to be an execution order problem but the values of the globals cannot be used to force the values of user parameters.

That's not true for all global parameters, but it is not documented. Yes and no. On www.selfgdl.com you find in section "context" for each global, in which context (either object type or script environment) the parameter is full available. This is an incomplete list, of course, but it is a beginning. AND there are globals, which are available in GLOB_CONTEXT=5, the one and only moment, when the PARAMETERS command does take affect on the local parameters.

@Mark
See
WIDO_ORIENTATION, where the content of the parameter comes from. PRINT is not the best command to debug a script. Most I use TEXT2 to print in floor plan or write out the value to an external file by using the text i/o addon. The last ist a pain, because you get tons of debug information, but the only way to find out, if the content of the parameter is blank in the situation, you need it.

Maybe you post your script to show, what you want to do.