Thanks for the replies. This is (sort of) the direction I was headed, although I like your specific idea below. I guess I'm still holding on to the synchronous world of coding I came from. ;) I feel like I'm always having to come up with ways to deal with Flex's asynchronous behavior, and it seems to require alot of additional code/handling (in my opinion).
Anyway, thanks for the specific "counter" idea below -- I'll give it a shot! --- In flexcoders@yahoogroups.com, "jerusalem_pilgrim" <[EMAIL PROTECTED]> wrote: > > Why can't you just use a "web service calls" counter in your code? > Every time a request goes out, increment it, every time you get a > response, decrement it. The "Print Receipt" button only gets enabled > if the counter is back to 0. > > > --- In flexcoders@yahoogroups.com, "byte.sensei" <byte.sensei@> wrote: > > data to produce a PDF receipt. The problem is, if a user clicks "Print > > Receipt" before all the save order web services have finished, then > > they only get a partial receipt. There's also not an easy way to > > determine if all the web service calls are finished, so I can't > > disable/enable the button based on that. >
