So it just happened again (horray!) - but this time I tried to catch some status. I just got that mysterious error caused by renaming an output Param.
As you know, any mishaps when renaming Params usually goes away if adding yet another Param and then immediately remove it again. But not this extra fancy exclusive error .
Nothing I do makes it go away, except for one thing: Reverting the Param name to its former name. Which is interesting (cache problem?).
This time I saved the definition, in .ghx format though, before and after the definition failed.
How to reproduce: I could rename the Param back to its former name - and add an extra Param and remove it again - and so make it work again. Renaming back to VSGUID will provoke the error back again.
Q: If you’re interested in the files I can send them to… some email address? (I was about to start refactoring the code since it’s the kind of component that evolves day for day, which is also why I started renaming Params, so the code is too messy to share here)
Fig 1. Param name “VSGUID” had former name “VSGuid” (if reverting to former name it will work again)
Of course I ran a compare on the “original” and “failing” .ghx files, but I couldn’t see any relevant differences there. Perhaps the .gh format would? (that can be reconstructed from the respective .ghx files if it need be)
Which mail adress? (if you want the files)