If use_mxp is set to 3 (No - never) setting it to either 1 or 0 will not work. You have to set it to 2 first.
A simple bug, but a bug none the less.
A simple bug, but a bug none the less.
use_mxp option bug
Posted by Zalethon on Mon 29 Oct 2007 05:30 AM — 2 posts, 11,779 views.
What do you mean "will not work", exactly?
Are you referring to setting the option in scripting? I tried what you said, and it worked OK, in the sense I didn't get an error code:
Also, the GUI configuration item updates correctly after setting it.
Do you mean, it looks OK in the configuration, but MXP is not correctly processed?
Are you referring to setting the option in scripting? I tried what you said, and it worked OK, in the sense I didn't get an error code:
/print (SetOption("use_mxp", 3)) --> 0 (means OK)
/print (SetOption("use_mxp", 1)) --> 0 (still OK)
Also, the GUI configuration item updates correctly after setting it.
Do you mean, it looks OK in the configuration, but MXP is not correctly processed?