From c751d40e070c6df907a526d7e3e17fc10611191e Mon Sep 17 00:00:00 2001 From: Monique Dewanchand Date: Mon, 30 Nov 2020 07:55:30 +0100 Subject: Cleanup hardcoded render percentage to factor conversion During revision of {D8952} one of the comments was to make a function that converts the render percentage to a factor. This to avoid code duplication. However the duplicated code was already all over the compositor code. So in order to avoid this code duplication for {D8952} I propose to first cleanup the duplicated code and build patch {D8952} based on this clean up. The method that converts the render percentage to a factor is put in the CompositorContext. Why? The CompositorContext keeps DNA information like the renderdata. DNA, and thus the CompositorContext, keeps the size of the render resolution in percentage (user oriented). The compositor needs the size of the render resolution as a factor. So the CompositorContext seems like the obvious place to have this conversion method. Why not in de NodeBase? The method could've been added to the nodebase, but I wanted to keep the nodebase as clean as possible and not put simple "conversion" methods into this base class. Also I didn't really like the call flow: you'd always have to get the renderdata size from the context and then convert. Putting it in the CompositorContext avoids this extra invoke of a call. Why not in the Converter? See nodebase. And the Converter seems more like a class for "structural" and complex node tree conversions. Not the simple conversions. Reviewed By: Sergey Sharybin Differential Revision: https://developer.blender.org/D9566 --- release/scripts/addons | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'release/scripts/addons') diff --git a/release/scripts/addons b/release/scripts/addons index 35c23b4db49..866dcad5aa6 160000 --- a/release/scripts/addons +++ b/release/scripts/addons @@ -1 +1 @@ -Subproject commit 35c23b4db494e58538a677c4fb0ec9ec1e8ffaa8 +Subproject commit 866dcad5aa6e45737f0634b835adcbc0871201e5 -- cgit v1.2.3