Ah, right you are Ivan. Thanks.

-Nathan



From: Ivan Busquets 
Sent: Wednesday, October 12, 2011 11:28 AM
To: Nuke user discussion 
Subject: Re: [Nuke-users] Do not display the error state of a node 
whichisinside a Gizmo

Both error and hasError are available in the expression parser, actually.

node.error returns true if using the Node would result in an error (even if the 
error comes from somewhere else upstream)
node.hasError only returns true when an error is raised within the node itself.

As J said, just using "hasError" as an expression in the disable knob of a Read 
node should do the trick there.



On Wed, Oct 12, 2011 at 10:38 AM, Nathan Rusch <[email protected]> wrote:

  I think J meant error instead of hasError. <node>.hasError() is a Python 
method, while error is the Nuke expression command.

  -Nathan

  -----Original Message----- From: Dorian Fevrier
  Sent: Wednesday, October 12, 2011 9:45 AM
  To: [email protected]
  Subject: Re: [Nuke-users] Do not display the error state of a node which 
isinside a Gizmo 


  Thanks for your answer!

  To be honest, I do not really understand. :(
  But it gave me an idea

  def returnFalse():
  return False
  node.hasError = returnFalse

  # Result: Traceback (most recent call last):
  File "<string>", line 1, in <module>
  AttributeError: 'Node' object attribute 'hasError' is read-only

  You was talking about overload hasError function?

  Thanks in advance. :)

  Regards,

  Dorian

  On 10/12/2011 06:22 PM, J Bills wrote:

    someone else might have a better answer, but off the top of my head,
    if you put "hasError" in the disable knob of the offending node, I
    believe that will fix it.

    On Wed, Oct 12, 2011 at 4:53 AM, Dorian Fevrier<[email protected]>  wrote:

      Hi Nuke users,

      I'm searching something that appear to be simple but I don't find any way 
to
      do this.

      I have a Gizmo node with some switch and read nodes inside.

      Following the case, the read node can have a bad file value (generated by 
an
      expression) and be in "ERROR" and "ERROR" is wrote on the Gizmo.

      Is there a simple way to avoid this node to return his "ERROR" state on 
the
      Gizmo?

      Actually, the error message is write on it but, because I use switch, the
      gizmo work perfectly...

      I hope someone already encountered this before.

      Thanks in advance,

      Dorian
      _______________________________________________
      Nuke-users mailing list
      [email protected], http://forums.thefoundry.co.uk/
      http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users



    _______________________________________________
    Nuke-users mailing list
    [email protected], http://forums.thefoundry.co.uk/
    http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users




  _______________________________________________
  Nuke-users mailing list
  [email protected], http://forums.thefoundry.co.uk/
  http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
  _______________________________________________
  Nuke-users mailing list
  [email protected], http://forums.thefoundry.co.uk/
  http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users





--------------------------------------------------------------------------------
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to