I've been looking into handling build interrupts so that we can
interrupt a build and allow a user to keep performing operations
without being blocked. However, the whole mechanism seems very limited.
I only want to interrupt and restart a build if the user made changes
in that same project, since the current build is now stale anyway since
a new one will be required after. I would like to be able to know what
caused the interrupt and only respond if necessary. For instance, if a
large project is being built in the background and the user is editing
files in a completely unrelated project, I don't want to respond to
that interrupt. Also, when a build gets interrupted and we want to stop
building, there is no mechanism in place for restarting that build
other than perhaps "touching" the project or something in it. Finally,
it appears the auto refresh manager is also causing builds to get
interrupted, which could put you in an infinite build loop if you're
restarting builds automatically after interrupts.
Perhaps this mechanism wasn't meant for these purposes...the docs I
read on this seem to indicate it was but are very vague. Any chance
this will be improved in a future version? Getting this working
properly would make a huge impact on perceived performance since the
user would be blocked a lot less. Any thoughts?
thanks,
-george
--------------------------
George Comninos
Adobe Systems Inc.