do someone know if the (auto)pattr support of envi is envisaged or not?

autopattr-and-envi

It escaped my notice that it wasn't yet supported. I can look at it for 

It escaped my notice that it wasn't yet supported. I can look at it for 
the next release.

Now that I have looked at it (I never use this object), it's pretty 

clear why it's not supported: we'd need to store the entire script in 

pattr. This is certainly possible, and could be done if there's enough 

demand, but it's not going to be easy to read or use the data.

Now that I have looked at it (I never use this object), it's pretty 
clear why it's not supported: we'd need to store the entire script in 
pattr. This is certainly possible, and could be done if there's enough 
demand, but it's not going to be easy to read or use the data.

Ok, I understand. Thank you for the quickness of your answer. I'm now 

converted to the pattr system as it's so useful with it's priority 

capabalities, objects view, and xml file saving. My old patch used 

the preset object that supports envi, but I guess it won't be too 

difficult to rewrite my patch to bypass the problem: I can put some 

numberboxes before envi, that autopattr will catch...

Ok, I understand. Thank you for the quickness of your answer. I'm now  
converted to the pattr system as it's so useful with it's priority  
capabalities, objects view, and xml file saving. My old patch used  
the preset object that supports envi, but I guess it won't be too  
difficult to rewrite my patch to bypass the problem: I can put some  
numberboxes before envi, that autopattr will catch...

Great, then we're all happy. "envi" will remain unpattrized, then.

you can dump envi data in a multislider object... it's the way i choose...

thanks for the tip, I going to look at it!

thanks for the tip, I going to look at it!
kb


(auto)pattr and envi