I've seen this before too. Think I got around it by using a Switch immediately downstream (input 1 set to the erroring node, input 0 set to whatever's just upstream of it) and setting the which knob to an expression like !input1.hasError. (Hi Matt, btw, long time no see!) -E
On Fri, Nov 22, 2013 at 3:33 AM, Matthew Doll <mattd...@gmail.com> wrote: > I have a group with nodes inside that have errors. I have their disables > set to hasError so nothing is broken, but the parent group displays 'ERROR' > despite there not being a real error. Is there a way to remove this display > from the group node? > > Thanks. > > _______________________________________________ > Nuke-python mailing list > Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > --
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
