Cool! From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Rusch Sent: Thursday, May 12, 2011 5:47 PM To: Nuke plug-in development discussion Subject: Re: [Nuke-dev] Simplest input switching implementation
Thanks for the reply Steve. I think you put me on the right track. I implemented _request and engine to only call input( i ).request() and input ( i ).get() respectively, and things seem to be behaving as expected. Thanks again, -Nathan From: Steven Booth<mailto:[email protected]> Sent: Thursday, May 12, 2011 12:02 PM To: Nuke plug-in development discussion<mailto:[email protected]> Subject: RE: [Nuke-dev] Simplest input switching implementation Nathan, I’ll defer to one of the more experienced developers, but I believe you still need to copy the channels (RGB? RGBA?, etc) from the selected input to the output in your _engine call, or nothing will be available downstream. It would be a pretty mindless copy, but it still needs be done, imho. Steve From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Rusch Sent: Thursday, May 12, 2011 11:53 AM To: Nuke-Dev Subject: [Nuke-dev] Simplest input switching implementation Hello all, I’m working on a plugin that does input switching based on some hash-related criteria, and I’m wondering what the most basic method of only passing through a single input would be (a la the Switch node). Right now I’m using a NoIop with my comparison code in _validate, and I’m wondering what steps I need to take to only pull data from one of my inputs. Right now I’ve pared it down to only call copy_info( i ), but even when I’m hard-coding in 1, it’s still returning the image data from input 0, so clearly I’m missing something mission-critical. Sorry for the basic question, but this has me pretty stumped, and I haven’t been able to dig up anything on the new mailing list forums. Thanks for any help, -Nathan (CONFIDENTIALITY NOTICE: The information contained in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient, or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email, or the information contained herein is strictly prohibited. If you have received this communication in error, please notify the sender by return email and delete this email from your system. Thank You.) ________________________________ _______________________________________________ Nuke-dev mailing list [email protected]<mailto:[email protected]>, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev (CONFIDENTIALITY NOTICE: The information contained in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient, or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email, or the information contained herein is strictly prohibited. If you have received this communication in error, please notify the sender by return email and delete this email from your system. Thank You.)
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
