Bumped into this app as an alternative to a quite noisy mechanical tally counter. You usually takes a tally of attendees just after starting a session, and this app is rather silent compared to a mechanical counter. It can be improved though.
Now, a mechanical counter is used for a tally of an whole area, but if you want to double check (or must do so due to regulations) it would be preferable to count seat rows and then sum them all for a larger area, in such a way that you can backtrack what you did.
One solution could be to increment a current tally for one row, then hit equal (=), which will leave the tally (number) on a stack of numbers. When you go on incrementing again, then it creates and increments a new tally. When you have all your seat rows you can sum them up for a larger area. This area sum is really a collapsed version of the row sum.
Sums could be tagged manually, or by a tally index. The tally index could be reset for each new area, or continue on the previous index. A collapsed sum should probably be tagged manually.
There should be an overall tally, and that would include all areas.
Bumped into this app as an alternative to a quite noisy mechanical tally counter. You usually takes a tally of attendees just after starting a session, and this app is rather silent compared to a mechanical counter. It can be improved though.
Now, a mechanical counter is used for a tally of an whole area, but if you want to double check (or must do so due to regulations) it would be preferable to count seat rows and then sum them all for a larger area, in such a way that you can backtrack what you did.
One solution could be to increment a current tally for one row, then hit equal (=), which will leave the tally (number) on a stack of numbers. When you go on incrementing again, then it creates and increments a new tally. When you have all your seat rows you can sum them up for a larger area. This area sum is really a collapsed version of the row sum.
Sums could be tagged manually, or by a tally index. The tally index could be reset for each new area, or continue on the previous index. A collapsed sum should probably be tagged manually.
There should be an overall tally, and that would include all areas.