I guess there is no way to get the parameter out of this state other than deleting it and readding it? Even if you set the default mode via Python this keeps happening!
Tagging @snaut for severity — let me know if this is annoying
Yo Dan
I’m putting in this SEVERE bug report Seriously though, this is rather severe for those of us that work in this domain of TD. We’ll get it solved in time for next release I think.
Hi. This is now fixed for builds 2025.31760 and later, but for what its worth, looks like this has been around since .defaultMode was introduced in 2023 it seems.
Work around in your case would be to remove the default expression, or change the constant value to something non-default.
Sorry for the inconvenience,
Rob.
It’s happening when you define a default expression for the parameter, but leave it at its default constant value.
When it loads up, it sees everything was at default, and wrongly decides to showcase the expression, ignoring the defaultMode setting.
Looks like the fix made it into 2025.31760 which is now available for download.
So just a heads up, there may be an issue with this fix causing parameters with default expressions to load up in constant mode (but still keeping the expression intact)
We’re investigating the situation.