Any way to bypass the "setting" command's hardcoded list?

Discuss and share scripts and script files...
Post Reply
Mesh
Posts: 956
Joined: 24 Mar 2008 21:22

Any way to bypass the "setting" command's hardcoded list?

Post by Mesh »

Is there any way to get the "setting" script command to support all options in XY's ini file? So that anything given as "setting name", if it exists, will be changed - as opposed to having a hardcoded list of supported settings?

The first time I hit this limitation was when I was trying to turn off the Recursion Checker for just one script. I wanted that particular script to run without any recursion errors, but I didn't want to turn it off globally. But I'm sure there are many other reasons to have the settings command not be hardcoded.

admin
Site Admin
Posts: 66254
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Any way to bypass the "setting" command's hardcoded list?

Post by admin »

No, that's not possible.

Mesh
Posts: 956
Joined: 24 Mar 2008 21:22

Re: Any way to bypass the "setting" command's hardcoded list?

Post by Mesh »

admin wrote:
No, that's not possible.

Short, but to the point. :)

Thanks for the quick reply.

serendipity
Posts: 3360
Joined: 07 May 2007 18:14
Location: NJ/NY

Re: Any way to bypass the "setting" command's hardcoded list?

Post by serendipity »

But you can still do this by reading/writing to the ini file.

update: Arrg, you would need to restart XY then. Hmmmm

Post Reply