There is a feature missing that was a problem during my last calculation. We had a group of "person groups", meaning 4 Families, some with 3 children, some without. Children are not paying, and partners share the same purse, so I created a "traveler" for each family. We wanted to split the money in a "fair" way, so that a family with more "eaters" (=children) pays more than a family with just two adults.
In my understanding, I would say, I needed a "weight" per traveler (=persons in this calculation group) that mirrors the relative payment. A family with 2 parents and 3 children would have "weight" 5, a single person would have "weight" 1 - and the couple without children would have "weight" 2 - the payments should then be split according to this weight: 5:1:2.
This would be a big improvement IMHO to this (already excellent) software. The weight could be a property of a traveler, when creating it, and changed later, let's say, because the group decides that one child in a traveler subgroup is so small that it does not count - so decreasing the weight should update the splitting accordingly, automatically.
However: The idea behind the feature in my head was that instead of entering amounts you can enter the weights, i.e. 5, 1, and 2 in your example for every family representative fictional person.
What I take from your remark is, that it is worth think about to declare the weight per person inside the trip.
There is a feature missing that was a problem during my last calculation. We had a group of "person groups", meaning 4 Families, some with 3 children, some without. Children are not paying, and partners share the same purse, so I created a "traveler" for each family. We wanted to split the money in a "fair" way, so that a family with more "eaters" (=children) pays more than a family with just two adults.
In my understanding, I would say, I needed a "weight" per traveler (=persons in this calculation group) that mirrors the relative payment. A family with 2 parents and 3 children would have "weight" 5, a single person would have "weight" 1 - and the couple without children would have "weight" 2 - the payments should then be split according to this weight: 5:1:2.
This would be a big improvement IMHO to this (already excellent) software. The weight could be a property of a traveler, when creating it, and changed later, let's say, because the group decides that one child in a traveler subgroup is so small that it does not count - so decreasing the weight should update the splitting accordingly, automatically.