Hi Joakim,
Ok so I have encountered a similar issue in the past and the reason is mostly likely that the editor is parsing the exposed expressions through the full list of bound expressions, not through the activated/compile paths. There is a less direct way to check for usage which essentially involves adding a recursive loop which checks the connections from each output node and goes through each expression to test each path, what is connected, and what is activated/deactivated. This is not built into the engine currently (although will be part of our new material translator which is going into experimental for 5.7).
Could you please share with me some code samples/screenshots of what your current setup is so I have a bit more context? And in the meantime I’ll dig out the code sample I have *somewhere* (lol) which does the parsing behaviour I described above.
Thanks,
Jon