topic Re: Re-lock parameters in Libraries & objects

Re-lock parameters

Bruce — Wed, 24 May 2023 09:40:50 GMT

I have a bunch of parameters that I don't really want the user to edit...but on the off-chance that they need to, I want to allow that.

So, I have created a menu in the parameters list, but have locked them all. A boolean parameter allows the user to unlock these for editing.

My question: how do I automatically re-lock these parameters when the user exits the settings window?

Re: Re-lock parameters

Barry Kelly — Fri, 16 Oct 2015 01:20:47 GMT

Maybe you could try ...

if GLOB_CONTEXT <> 5 then
Boolean_parameter = 1
Parameters Boolean_parameter = Boolean_parameter
endif

That way as soon as to close the object settings the lock parameter should get turned on again.

I haven't tested this but it might work.

Barry.

Re: Re-lock parameters

Bruce — Fri, 16 Oct 2015 01:42:34 GMT

Perfect! A most excellent solution. Thanks very much!

Re: Re-lock parameters

Mario Sacco — Fri, 16 Oct 2015 11:37:27 GMT

Beware the use of global, it's a "Deprecated Global Variables".
If you use it in v19, Archicad will not benefit of predictive computation.
In v20 GLOB_CONTEXT used in parameters script or master script will have always the value 2.

http://download.graphisoft.com/ftp/techsupport/downloads/GDL/GDL%20changes%20in%20ArchiCAD%2019%20v1.1.pdf

Re: Re-lock parameters

Bruce — Sat, 17 Oct 2015 00:37:54 GMT

Thanks for the heads-up & the link. Seems I'll have to look for another solution. Cheers.

Re: Re-lock parameters

Bruce — Sun, 18 Oct 2015 19:56:21 GMT

Turns out it only affects the parameter script (as you mentioned). If I move the GLOB query into the Master Script, it should still work.

Cheers!

Re: Re-lock parameters

Mario Sacco — Sun, 18 Oct 2015 20:53:42 GMT

Bruce wrote:
Turns out it only affects the parameter script (as you mentioned). If I move the GLOB query into the Master Script, it should still work.

Cheers!

If you use PARAMETERS command in master script it works as parameters script. It's not written, but I'm quite sure it's so.
The master script to work fine must not have PARAMETERS command.
I'm sure 95 %
😉

Re: Re-lock parameters

Bruce — Sun, 18 Oct 2015 22:56:03 GMT

In the master script I put:
IF GLOB_CONTEXT <> 5 THEN Boolean_parameter = 1

In the parameter script I put:
PARAMETERS Boolean_parameter = Boolean_parameter

Seems to work just fine. Haven't tested it in v19 yet.

Re: Re-lock parameters

Mario Sacco — Mon, 19 Oct 2015 04:42:14 GMT

Bruce wrote:
In the master script I put:
IF GLOB_CONTEXT <> 5 THEN Boolean_parameter = 1

In the parameter script I put:
PARAMETERS Boolean_parameter = Boolean_parameter

Seems to work just fine. Haven't tested it in v19 yet.

It's not simple.....
The parameter Boolean_parameter in PARAMETERS script depend from a set in master script; it makes master script working as parameter script.

Let me know your try, It's a huge problem for many GDL developer.

Re: Re-lock parameters

Bruce — Mon, 19 Oct 2015 06:47:23 GMT

Well I don't have v19 to test it in yet, but it works just fine in v18.

Re: Re-lock parameters

Anonymous — Mon, 19 Oct 2015 07:15:58 GMT

In version 19 will work, in 20 - no.
Instead of the GLOB_CONTEXT, should be applied GLOB_VIEW_TYPE. Press the Check Script button in v19, and will be generate the warning in the GDL Editor.
All GLOB_ canceled, PEN_OF_RGB, MATERIAL_INFO, TEXTBLOCK_INFO - how many items will have to redo. Not very pleasant innovation in GDL.

Re: Re-lock parameters

Anonymous — Mon, 19 Oct 2015 07:26:13 GMT

I could not agree more with SL_GDL!
To remove context and other globals is insane!
Anyone using context or view dependant code WANTS to have objects change dependant on views!
The line of "in teamwork two people can see the object differently depending on the view" is the whole point!!!!! Not an argument for removing the option!

Re: Re-lock parameters

Barry Kelly — Mon, 19 Oct 2015 08:10:45 GMT

No sorry my solution doesn't work in 19 - not the initial release anyway.
It is supposed to work when the next hotfix is released to give us time to change our scripts before it stops working again in 20.

But just what can we change our scripts to.
I use GLOB_CONTEXT quite a bit.
This is a classic example of how.
Or in a schedule I use it to control the 2D symbol of an object so it is not rotated/reversed just because the object was placed that way.

Can someone from GS please explain if we can no longer use GLOB_CONTEXT how can we set a parameter based on the context of what is happening to the object at that time?
i.e. how do we get around this particular problem of resetting a Boolean parameter when we are not viewing the object settings dialogue.

This would be greatly appreciated.

I agree with Kistian in that we want objects to change dependent on the views - teamwork or no teamwork.
What is the solution?

Barry.

Re: Re-lock parameters

sinceV6 — Mon, 19 Oct 2015 22:10:48 GMT

Hello.

It is, indeed, a simple but interesting issue.
As far as I can tell, objects will be able to change depending on the views, just coded differently. You will be able to use GLOB_VIEW_TYPE, GLOB_PREVIEW_MODE and GLOB_FEEDBACK_MODE to set how the object looks, but not change its stored parameters just by changing to another view type. So, in this particular case, if the user has set a value for the boolean parameter, the parameter script won't be able to change what the user has set as a stored parameter... or at least this is how I understand the GDL changes document.

I think the part about teamwork is referring to instances where an object might change stored parameters based on a view that another team member is using, something like if I'm looking at an object with 2 pieces set as an integer and a team member reserves that object, opens another type of view and because of that the object changes that parameter to 3, then it is no longer reliable what the two people are looking at. You could still code in that the object should display 3 pieces in that view or 2 in the other, but without changing the original 2 pieces set... something like that.

I can see the use for the example provided in the thread, re-locking a parameter once the dialog box closes; but don't think it will work in future versions.

Of course... I could be ENTIRELY wrong in what I've said until further and deeper information is available.

Best regards.

Re: Re-lock parameters

Laszlo Nagy — Mon, 19 Oct 2015 22:17:46 GMT

Just for reference here is the document that outlines what has changed, why and what to do:

http://download.graphisoft.com/ftp/techsupport/downloads/GDL/GDL%20changes%20in%20ArchiCAD%2019%20v1.1.pdf