Fix (unreported) compositor resolution propagation broken by some nodes

Some operations may use no preferredResolution ({0, 0}) when calling determineResolution on inputs to check if they have resolution on their own. See MixOperation or MathOperation determineResolution implementation. In such cases {0, 0} resolution ends up being set when an input doesn't have own resolution, breaking propagation of the original preferredResolution. They don't mean to set it as resolution, it's just a check.

This patch only allows to set valid resolutions (>0). When it's 0 it may be understood as "No preferred or determined resolution" so it should not be set to give output operations another chance of finding a proper resolution by calling determineResolution again with a different preferredResolution.

Test file:
{F9932526}

Reviewed By: #compositing, jbakker

Differential Revision: https://developer.blender.org/D10972

3 files changed, 0 insertions, 0 deletions

diff --git a/release/datafiles/locale b/release/datafiles/locale
-Subproject 2cef4877edc40875978c4e95322bb5193f5815b
+Subproject f7b706dd6434db2d752f47c4b8c3148b2990fd7
diff --git a/release/scripts/addons b/release/scripts/addons
-Subproject bcd08a9506d33bdd7358201031b04d041ef22d9
+Subproject 1dbdb95ed93a8b96d12e42e17249f6e2cdd2461
diff --git a/release/scripts/addons_contrib b/release/scripts/addons_contrib
-Subproject f948f658ba33eb670a65e0bba058d43138abea7
+Subproject 5523cbaed60719960f5f7b2486925145ecbe81e