UXP - reading/writing effect's hidden arbitrary params?

Is there a way to read/write effect’s hidden arbitrary parameters, like we could do with ExtendScript by treating them as utf-16 strings?

My probes for value reads and writes throw errors:

value reads: 
param "Plugin UUID";
timeVarying=false keyframes=false; 
getStartValue -> undefined undefined; 
getValueAtTime(0) threw getValueAtTime() is not supported for Color, MogrtText, or MogrtComment type component parameters. Use getStartValue() to get the current value of component parameters of those types.; 
getKeyframePtr(0) threw Error: Illegal Parameter type; 
raw keyframe: object 
keys=[] value: undefined keys=[]
writeProbe: {
"result":0,
"paramIndex":3,
"createKeyframe":"keyframe threw Error: Illegal Parameter type",
"startValue unchanged":"no keyframe",
"startValue .value = string":"keyframe threw TypeError: Cannot set properties of null (setting 'value')",
"startValue .value = {value}":"keyframe threw TypeError: Cannot set properties of null (setting 'value')",
"startValue .value.value = string":"keyframe threw TypeError: Cannot read properties of null (reading 'value')"
}
1 Like

Can I get any feedback on this? This capability to get/set hidden arbitrary parameter values is essential for us to be able to move on from CEP to UXP extension.

@Bart While they might be able to be listed, I’m doubtful that they would be able to set. As it stands a mogrt properties cannot be set by UXP, but they can be retrieved and listed.

There is a long standing thread here about this: MOGRT Parameters in UXP availabilty - #6 by Billy_Ward

While hidden params are different from mogrt params, they might fall under the same category in terms of migration from CEP to UXP.

Adobe might have more insight.

1 Like