> Great. What are you wanting the counter function to do? Maybe I can
> offer a suggestion or something.
I've got it working: I'm converting my ticket-sales tracking pages to
a form based interface instead of just me writing stuff down
explicitly.
I actually had a python script being run generating {p}.total pages
before, largely since I didn't realise there was a counter function,
and didn't know form commands well enough.
So I've got a group of people who have checked out tickets to sell, a
group of tickets that have been sold, and a group of tickets that have
been reserved by mail.
I simply needed a system to count how many are reserved, so I can stop
booking tickets when they've run out.
essentially:
[template first][(counter = {:nSeats} id=remaining)]
[template each]
[r][c]{+:amount}[(counter - {+:amount} id=remaining)]
[c] {+:groupName}
[c] {+:seller}
[template last][r][c]remaining: [(counter + 0 id=remaining
output=true)]
Except it's actually two templates and the code is a bit more spread
out.
I assume theres a better way to display a counter than the last line
of code, but I was too tired to find it.
I now use the same header to control ticket sales for 5 shows and the
party. It's something of an improvement.
> Good. Don't bother to upgrade the codebarn docs, as that was supposed
> to have been deleted in favor of the new help system. Didn't realize
> those links were still there.
The new help system has potential, but I think more usage oriented
help-texts would be more useful than the description oriented texts I
saw...
The system is very similar to matlabs help command. I like it.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
