The latest which is more fleshed out and about all I'm going to look into this :)
http://pastebin.com/Y7emN2sA On Mon, Feb 28, 2011 at 3:09 AM, Nathan Dunsworth <[email protected]>wrote: > Probably should return node and break the loop when nodes is empty. 3am > hacking not fun. > > http://pastebin.com/b4Qk7AZ9 > > > On Mon, Feb 28, 2011 at 2:48 AM, Nathan Dunsworth > <[email protected]>wrote: > >> When selecting multiple nodes and creating a new one, Nuke messes up the >> node trees of all dependent nodes of the selected ones. >> >> Nuke 4.x had some issues but they have become more pronounced since 5.x. >> >> How to see an example? >> >> Create 3 Read nodes and connect a Grade to each one. Now selecting only >> the Read nodes create a Blur Node. >> You will notice all Read nodes Grades are connected to the single Blur >> Node which == Bad. >> >> Proposed fix. >> >> This fix still maintains the ability to work with the following example. >> >> Two nodes are selected, a Camera and Scene Node. >> >> Creating a ScanlineRender node will connect the proper inputs to the >> selected Camera and Scene. >> >> The proposed fix does have issues with some nodes and there >> Node.optionalInput. You will notice a badNodes var. >> >> A new python function Node.maskInput() for retrieving a NukeWrappers mask >> input would alleviate this problem. >> >> http://pastebin.com/dVEA3sJz >> > >
_______________________________________________ Nuke-dev mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
