And for the record, I am certainly no friend of the PrintJob class. It's
poorly written and I've pointed out its numerous flaws in previous posts
to
this list.
Yes, it shouldn't have been coded to work the way it does. The way it
works
is poorly thought out. But, that doesn't mean that it's a bug because it
technically is working exactly as it should.
I think we're in a semantic discussion about what is and isn't a bug here. I
agree with Steve W: I can't see that the Flash engineers would have
specifically designed it with this behaviour in mind, and the behaviour is
not what the function ought to do from a user's perspective, therefore it's
a bug. (Otherwise you could argue that *every* program is doing exactly what
it was programmed to do, therefore nothing is a bug).
I would argue that Flash's 'is it hanging' test should be given a hook that
the printJob (or other) classes could talk to, which essentially stops it
checking until the function is returned. Anyway, I was under the impression
that it counted number of lines of code executed, not time taken. In
particular, your discovery that this doesn't occur in a barebones movie
would seem to imply that it *is* a bug, because somehow the synchronicity
isn't being maintained.
Danny Kodicek...I think I remember you from my Director days, so long ago.
That's me. And I remember that you were a bit belligerent then too ;)
Danny
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
