Forum General discussions About this site Problems and solutions in GDL Forum rules and functions

[Lingwisyer GC]

Péter Baksa wrote:

The 2d script doesn’t know about the variables in the UI script.

Everything else is in the Master Script. It is just a ‘text2 a’ and a ‘ui_outfield a’ found in their respective scripts.

Péter Baksa wrote:

You can show variables and current value of parameters with UI_OUTFIELD.

That works. I never thought of using an infield for displaying a parameter.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

In the 2D Script, I have a TEXT2 that outputs the values.
In the Interface Script I have an UI_INFIELD that outputs the same values.

Neither of the scripts contain anything that modifies any of the parameters so they should both be reading the same values from the Master Script, yet only the 2D Script is returning the correct values.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

Should probably reword “profile set” to “value of myProfileIdx”.

Some of them probably are, but it does not even return the default values.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

So, I included the following in my Interface Script;

	n2 = REQUEST ("Profile_default_boundingbox",  myProfileIdx, _xMin, _yMin, _xMax, _yMax)

	ProWidth = abs(_xMax - _xMin)
	ProHeight = abs(_yMax - _yMin)
	SquareV2 = ProHeight / ( cos(phi) )

but they appear to have no effect. ProWidth returns 50, ProHeight returns 100 and SquareV2 returns 0 no matter the size of the profile set…

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

How do you set multiple targets and operators?

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

n = REQUEST{2} (“Building_Material_info”, name_or_index, param_name, value_or_values)

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

You could use SUBGROUP{2} and set the cut surface there to be the same as your target.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

Would I need to duplicate the request in the UI Script? I removed the two parameters from the Parameter Script and inserted an infield for them but they do not change when the selected Complex Profile is changed.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

See linked thread for more information and resolution.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

This object has the option to use complex profiles. The issue only occurs when a complex profile is used. The original two equations include SquareV2 and if skipped, the 2D and 3D resolve correctly.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

The Parameter Script needs only to run after the other scripts have run or when it is first initiallised.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

Whelp. Forum will not allow me to edit that post. It did not actually fix anything. Had forgotten to change some substituted values back to the parameter Squarev2.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

Phi in the original script was substituted with 35.

Well… that was unexpected. So I added the “isFirstRun” query to the start of my Master Script followed by a “GOTO MasterEnd” and it appears to all be working. My limits are even showing in the Parameter Script, even though SquareV2 is not being resolved.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

I am a little confused by your script.

That is just a clipped section of my script.

ProHeight = abs(_yMax - _yMin)
SquareV2 = ProHeight / ( cos(phi) )

Due to requests not being resolved in the Parameter Script, this section will return an incorrect value when it is run for this script.

n = APPLICATION_QUERY (“parameter_script”, “firstoccasion_in_progress”, isFirstRun)

So I would include that query in my Master Script and get it to not execute if the Parameter Script has been run more than once?

If isFirstRun > 1 then goto MasterEnd

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Lingwisyer GC]

Setting SquareV and Pitch_off to only update when they are modified has no affect. They only affect each other.
Disabling the update of these two allows the script to work, but results in it being possible for values to show that are not the ones being used, being outside the min / max.
If I swap parameter “SquareV2” with 0.305 the Master Script works as it is suppose to for that value.

I think you might be right about the Parameter Script being run multiple times, or at least run before the 2D and 3D Scripts. Is there a way to force the Parameter Script to only run once after executing the 2D and 3D scripts?

“SquareV2” does not resolve in the Parameter Script due to being calculated using a requested value, yet if I say “PARAMETERS SquareV2 = 0.305” the incorrect values are still used. This seems to imply the the Master Script is run, then the Parameter Script is looped before the 2D and 3D scripts OR it is just getting confused by the input value from the Parameter Script, and the value calculated in the Master Script and returning 0.

Returning 0 is more desirable then returning incorrect values.

Ling.

AC18-23 AUS 4006
Self-taught, bend it till it breaks.
Win7 | E5620 x 2 | 24GB | K2200

[Author]

Posts