Add per-recipe setting to show/hide the total I/O

[veger]

As discussed in #338 it might be more convenient to make the recipe total I/O configurable per recipe, sicne we cannot figure out a 'catch all' that covers all of the seablock, py and space-age, etc. mods...

The screenshot shows the same recipe twice, one with I/O enabled and one disabled:

Note that the label is renamed to "Show total Input/Output"

[shpaass]

Nice!
What do you think about naming the option Show total input/output?

[DaleStan]

I think there's space for more improvement, to improve discoverability, but this could come later.

When setting (but not deserializing) RecipeRow.entity, add showTotalIO = value.has_vector_to_place_result && recipe.products.Length > 1, or maybe |= instead of =. (Which requires adding and setting a has_vector_to_place_result property.)

I don't think that needs a preference for how many products the recipe has before setting showTotalIO, but then again, I thought that a number-of-products preference was good enough in the previous version of this feature.

[veger]

When setting (but not deserializing) RecipeRow.entity, add showTotalIO = value.has_vector_to_place_result && recipe.products.Length > 1, or maybe |= instead of =. (Which requires adding and setting a has_vector_to_place_result property.)

You mean automatically setting showTotalIO to true, if the recipe is created and has more than on product?

I do not understand what you mean with value.has_vector_to_place_result though...

[DaleStan]

Oh, I'm sorry. I meant to add a link to https://lua-api.factorio.com/latest/prototypes/CraftingMachinePrototype.html#vector_to_place_result

It appears vanilla only sets this property on miners (which only have one output for YAFC) and the recycler.

[veger]

It took a bit of refactoring the 'setter' in order to process the showTotalIO |= ... properly.

With this change the recipe automatically has its showTotalIO set to true, when the crafter entity has an 'unloader' and the recipe produces more than one product.