That is exactly what I find should be correct. On Mon, Jun 6, 2016 at 3:26 PM, gandalf3 <[email protected]> wrote:
> I'm not sure this would be a "hard coded coupling" in the usual sense > (which I agree is something best avoided). > As I understand it, this node basically tells subsequent scale nodes to > use nearest interpolation. It does nothing itself to modify the data. > > Afaik no other node changes the behavior of other nodes like this, and > it's totally against what I expect when using a node; I expect a self > contained function which takes data in, does stuff, and passes data out, > without caring about what happens to that data before or after. > > When I first heard of this node, I expected something rather like the > initial suggestion <http://www.pasteall.org/pic/103972>. > Inside: http://www.pasteall.org/pic/103974 > > > On 06/06/2016 11:30 AM, Knapp wrote: > > The real problem is not having good education about the tool. > > When a new tool like this is added, it could be said in the cool new > > features release that it must be combined with the other node. That > should > > give enough people a heads up that the rest will catch on. Of course it > > must also be in the masual. > > Douglas E Knapp > > > > On Mon, Jun 6, 2016 at 5:31 AM, Troy Sobotka <[email protected]> > wrote: > > > >> The coupling of nodes hard coded is perhaps one of the most destructive > >> paths for Blender. > >> > >> Instead, perhaps effort should be put into providing a means to import > and > >> export node trees and groups as singular nodes? > >> > >> The greenscreen coupled up node from hell is an example of a worst case, > >> and it would be a shame to see this ill trend continue any further > instead > >> of tackling the issue at the core. > >> > >> With respect, > >> TJS > >> > >> On Sun, Jun 5, 2016 at 5:55 PM Aaron Carlisle <[email protected]> > >> wrote: > >> > >>> Currently, the Pixelate Node [1] is difficult for new users to know how > >> to > >>> use because > >>> they do not know that they need to add a scale node before it inorder > to > >>> get desired results. > >>> To easily fix this I purpose that a scale operator is added to the node > >>> making it easier to use. > >>> > >>> > >>> - Aaron Carlisle > >>> > >>> > >>> 1. > https://www.blender.org/manual/compositing/types/filter/pixelate.html > >>> _______________________________________________ > >>> Bf-committers mailing list > >>> [email protected] > >>> https://lists.blender.org/mailman/listinfo/bf-committers > >>> > >> _______________________________________________ > >> Bf-committers mailing list > >> [email protected] > >> https://lists.blender.org/mailman/listinfo/bf-committers > >> > > > > > > _______________________________________________ > Bf-committers mailing list > [email protected] > https://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
