@gregsn : Simple example (new node interface)
I want to access Value or Color (INodeIn)
FX.SetSubType(
new Guid[]{
typeof(IValueData).GUID,
typeof(IColorData).GUID,
},
“Value Color mainly”);
With “33.7” that would be working.
With new “AND” connection that is not (you can’t connect it anywhere instead).
And in that case you can’t create a common interface.
Plus, adding new interface means that for every pair you’d want to accept you would need to add interface on every types, as an example, type T, U,V
if you need T and U, you need I1 and modify T and U that they implement I1
if now you need U and V somewhere else, you need I2 and modify U and V
and so on. (I’m not even speaking of the case where T,U and V reside in different assemblies) This is more like a workaround to patch the workaround…
Instead with 33.7, you simply set your node to accept T and U, if you need to accept Z (without source code access), you can add it seamlessly. This was working, now it’s gone…
Also maybe I should have done an example patch, but here is what you have with box2d (just tried with b35)
I made the example using the simplified example.
ValueTestNodeIn.zip (11.2 KB)
Connection is not accepted (as you can see the “Connected pin” is false), but link is visually present. So I have doubt that the new type system is still working properly.
So basically ,this is broken, please fix…