rolloverPar attribute display shows binding when off TD25370

Bugs
1

I’m not sure if this is by design or not, but if a par is rolled over, and a bind expression is present, the info popup displays a readout stating that the parameter is bound even though neither has an active bind mode. In trying to create a simple example, and playing around with how it evaluates when bound nodes are cut and paste, i was able to paste a node and then the bind expressions go from optimized to unoptimized, and finally stumbled upon a truly odd behavior, the attached example, in which neither node has a bind expression or is in bind mode, and yet both are bound to each other. worth some investigation

TDMovieOut.0
TDMovieOut.01920×1080 151 KB

bind idiosyncrasies.toe (3.6 KB)

1 Like
2

I am seeing some odd stuff here and putting in our bug queue. However it looks to me like the image shows you looking at the same par dialog, so that’s why they both show that they’re bound!

3

Lol yes, been staring at this too long. The initial reason i put the example together stands though, that if you take this example and turn on the bind expressions in base 1, then cut and repaste base2, the bind references stay unoptimized, and don’t relink properly until a cook. If you turn off the bind expressions, the rollover still says they are bound