Parameter Script Compatibility

[Anonymous]

According to the GDL Reference Guide, "View or project dependent global variables should not be used in parameter scripts (or master scripts run as parameter script) to avoid the parameter script run occasions and the resulting parameter values becoming context dependent, inconsistent within the planfile."


This new setting in ArchiCAD 20 is affecting many of our custom objects that use the Glob-Scale variable in the Parameter script. Any suggestions for a work around? I have tried moving the Parameter code to the 2D section without success.

How are folks dealing with this in their custom objects?

[Anonymous]

Same question here - I have an object where I used GLOB_HSTORY_ELEV and GLOB_HSTORY_HEIGHT as well as all the geolocation GLOB parameters.
Now ina AC20 it does not work according to this:
http://gdl.graphisoft.com/reference-guide/global-variables

What's the guideline for GLOB paramaters now ?

[Piotr Dobrowolski]

Avoid using them in parameter script and masterscript...

Best Regards,
Piotr

[Anonymous]

Piotr wrote:
Avoid using them in parameter script and masterscript...

Best Regards,
Piotr

I use them in 2D Script,
and it does not work as well.

It looks like they don't work anywhere ...

[Barry Kelly]

philips wrote:
I use them in 2D Script,
and it does not work as well.

It looks like they don't work anywhere ...

As far as I know they should work fine in 2D or 3D scripts.
Just not in master and parameter scripts.

If you have an example of something not working maybe you can attach it to a post and someone can have a look.

Barry.

[Piotr Dobrowolski]

philips wrote:

Piotr wrote:
Avoid using them in parameter script and masterscript...

Best Regards,
Piotr

I use them in 2D Script,
and it does not work as well.

It looks like they don't work anywhere ...

If You are the one that asked WSC about it, You have in return my object that works.

Best Regards,
Piotr

[Anonymous]

My opinion on changes to global and parameter scripts.

View based globals should not affect the parameter script
Project based globals should be allowed to affect the parameter script

why?
GLOB_CONTEXT
yes, could change in different views
parameters shouldn't change due to the view

GLOB_VIEW_TYPE
yes, could change in different views
parameters shouldn't change due to the view

GLOB_SCALE
yes, could change in different views
parameters shouldn't change due to the view

GLOB_DRAWING_BGD_PEN
yes, could change in different views
parameters shouldn't change due to the view

GLOB_FRAME_NR
yes, could change in different views
parameters shouldn't change due to the view

GLOB_FIRST_FRAME
yes, could change in different views
parameters shouldn't change due to the view

GLOB_LAST_FRAME
yes, could change in different views
parameters shouldn't change due to the view

GLOB_EYEPOS_X
yes, could change in different views
parameters shouldn't change due to the view

GLOB_EYEPOS_Y
yes, could change in different views
parameters shouldn't change due to the view

GLOB_EYEPOS_Z
yes, could change in different views
parameters shouldn't change due to the view

GLOB_TARGPOS_X
yes, could change in different views
parameters shouldn't change due to the view

GLOB_TARGPOS_Y
yes, could change in different views
parameters shouldn't change due to the view

GLOB_TARGPOS_Z
yes, could change in different views
parameters shouldn't change due to the view




GLOB_NORTH_DIR
project based, not view based.
the library part needs to know what this is...
this is a fixed value that will not change based on views
this needs to affect parameters, i.e. solar panels need to face the sun, sunshades to to adjust due to east/west/north/south orientation


GLOB_PROJECT_LONGITUDE
project based, not view based.
the library part needs to know what this is...
this is a fixed value that will not change based on views
this needs to affect parameters, i.e. solar panels need to face the sun, sunshades to to adjust due to east/west/north/south orientation


GLOB_PROJECT_LATITUDE
project based, not view based.
the library part needs to know what this is...
this is a fixed value that will not change based on views
this needs to affect parameters, i.e. solar panels need to face the sun, sunshades to to adjust due to east/west/north/south orientation


GLOB_PROJECT_ALTITUDE
project based, not view based.
the house may need to know this. higher altitudes may need more insulation, etc...

GLOB_PROJECT_DATE
project based, not view based.
May be i want the library part to change its behavior after a certain date, regulation change on or after a date...




GLOB_WORLD_ORIGO_OFFSET_X
project based, not view based.

GLOB_WORLD_ORIGO_OFFSET_Y
project based, not view based.

GLOB_CUTPLANES_INFO
yes, could change in different views
parameters shouldn't change due to the view

GLOB_STRUCTURE_DISPLAY
yes, could change in different views
parameters shouldn't change due to the view

LAYOUT_CURRENTREVISION_OPEN
yes, could change in different views
parameters shouldn't change due to the view

GLOB_HSTORY_ELEV
not view based
the library part may need to know what this is.

GLOB_HSTORY_HEIGHT
not view based
the library part may need to know what this is.

GLOB_CSTORY_ELEV
yes, could change in different views
parameters shouldn't change due to the view

GLOB_CSTORY_HEIGHT
yes, could change in different views
parameters shouldn't change due to the view

GLOB_CH_STORY_DIST
yes, could change in different views
parameters shouldn't change due to the view

GLOB_SUN_AZIMUTH
yes, could change in different views
parameters shouldn't change due to the view

GLOB_SUN_ALTITUDE
yes, could change in different views
parameters shouldn't change due to the view