onChanged() triggers for the first time before all of the properties are loaded, so it can fail to compute properly at that stage, depending on the load order. However, it's not necessary to compute geometry in onChanged() at all, because that's usually supposed to happen in execute() anyway. The solution here is to just not do onChanged() at all. Fixes #13558
25 KiB
25 KiB