http://www.edgewall.org/docs/branches-0.12-stable/epydoc/trac.ticket.api.ITicketChangeListener-class.html
shows me the syntax/interface for a ticket change listener but doesn't
give me a lot of context for when it is called, what I can safely do
in a listener, etc. I'm running into a problem in my listener that
only shows up on large datasets in our test environment but not in the
small dataset in my development environment and I'd like to understand
timing and context so I know where to look for my problem. Is there
some tutorial or other documentation that will tell me how listeners
interact with the system and with each other? For example, if my
listener saves a ticket, does it get called again recursively so I
have to be reentrant? Does another call get deferred until this call
ends? When do other listeners get called for the change my listener
saves?
Here's what I'm trying to do: when a field related to scheduling
tickets changes, do a minimal schedule recalculation. So, if the
estimate for a ticket change from 8 hours to 16, any following work
will start a day later or this task will start a day earlier. In the
latter case, I'll do all my calculations then have a new start date
for the ticket that the listener got invoked for. When I save that
change -- inside the listener -- what happens?
Chris
--
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
