When a trap has been entered as gone (usually in our case landslide or avalanche) it might be good if the Trap condition is automatically populated with something like null or not applicable as the current options re condition are not very relevant.
There should also be a section for “destroyed” or “munted” as well as “gone”.
Additionally if a trap is unusable/out of service/gone maybe the trap on the line could be grayed out until replaced fixed etc.
Agreed, this seems sensible.
In answer to your additional request, under ‘Condition’ you will find ‘Disabled’. This will grey out the icon, and remove that period from the trap nights reporting. Automatically apply that in certain states is something we can look at.
The Trap Status and Condition fields are a little ambiguous and cross purpose. We’re discussing some changes to make these clearer and easier to work with.
Cheers,
Andy
Any progress on potentially getting an extra departure status for “trap gone, needs replacement”? Or even just amending the wording of “disabled” to something a bit more intuitive, for instance “disabled/missing/removed”, “inactive”, “out of service”, “not able to catch”…?
I feel that most casual trappers (i.e. infrequent app users), already a bit stressed about having found their trap destroyed/stolen, may not notice that the departure status has defaulted to OK, or may be confused enough about what status to pick that they just give up and leave it on “OK” as the default. I definitely remember the first time I needed to set a non-default status going through the dropdown thinking “no, it doesn’t need repair because it’s gone, and no, it’s not disabled because I can’t reenable a trap that isn’t here, so what do I put?!”.
The functionality of the “disabled” status greying out the icon etc. works really well when set, it’s just that trappers in my various groups don’t seem to be clicking on it!