LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Quit a library but keep going

    Employee
    Posted 12-20-2009 20:44

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: PGeee

    I want to exit a library (because of zero records in an input fle) but I want all dependant libraries outside of that to still run,. ie. I want to keep the clocks connected

    ie I want to achive following psuedo code

    if no records, exit library, and avoid remaning nodes in that library


  • 2.  RE: Quit a library but keep going

    Employee
    Posted 12-21-2009 06:47

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    If I understand you correctly, you want to look at the function
    setSuccessReturnCode...and specifically, you want to look at returning 203, I believe.

    From the online manual for setSuccessReturnCode for returning 203:

    Any nodes wired to the output will not execute, but any nodes wired to this node's outclock, or any of the outclocks of any nodes wired to this node's output will trigger. This behavior allows for this node to prevent other nodes from executing on the data, but to allow nodes clocked to a higher composite to still execute as if all nodes were executed.

    Cheers
    Rich


  • 3.  RE: Quit a library but keep going

    Employee
    Posted 01-27-2010 21:51

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: PGeee

    Thanks, that 203 option sounds good, how do I test for zero records on an input to a noide, ideally a filter


  • 4.  RE: Quit a library but keep going

    Employee
    Posted 01-29-2010 13:43

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    If that is all you want to do, you should use the node Meta Check, which is in the Metadata category of core. It has options for testing minimum and maximum record counts, and can also be configured to error, or cause clocked nodes to fire, etc...(similar behavior to what the setSuccessReturnCode behaviors are).

    Cheers
    Rich