Multiple of same items

[jagjordi]

First of all thank you for this absolutely awesome application.

I am consiering the following situation: I carry some spare of the same stuff that I wear, for example I have a baselayer that I wear and I have the same one in my backpack as spare.

I am trying to find the best way to handle this, now I can think of 2 ways, each with some drawback:

• Duplicate it and mark one as worn and the other not
  • Pro: correctly categorized in the pie chart as worn and base weight
  • Con: creates a duplicate that I have to manually keep track
• Mark it as 2 units
  • Pro: I dont have to duplicate it and keep track separately in the list
  • Con: can't keep track of work/baseweight correctly

Is there any other way to handle this situation? Perhaps it would be good to add some specific condition/option either to mark only one as worn, or have a way of handling multiple copies of the same entry. The later option would also be good, because you couuld have the same item in multiple categories, for example in Clothes and Spare clothes:

[jhollowed]

Belated response here, but FYI this is already a feature.

In LighterPack, whenever you mark an item as "worn", and set the quantity to anything greater than 1, then each quantity of the item beyond the first will contribute to Base Weight rather than Worn weight.

That is, if I enter "Pair of socks" with a weight of 2 oz, set it to "worn", and update the quantity to "3", then the result is:

• One "Pair of socks" increments Worn weight by 2 oz

• The second and third "Pair of socks" increments Base Weight by (2 oz + 2 oz) = 4 oz

This feature specifically exists so that you can enter worn items, for which only one will be worn at a time.

It's a bit of a hidden feature though, which many users don't know about. This feature actually leads to some confusion when people try to enter their trekking poles as a quantity "2", and then mark them worn. One goes to Base Weight, and one goes to Worn weight, without any clear notification of that to the user.

Or maybe I misunderstood your comment.