Hi Icon
Thanks for your reply
WGTicon: if it;s an issue with flash, such as , how it interacts with a browser, not only there maybe little we can do, but it's also very hard to track down.
Yeah, I totally get that as that would be a Flash issue as this happens on all browsers, the point that I was trying to make and failed, was has WGT been in contact with Adobe about this issue and is there a workaround for you, or do we have to sit and wait for a new Flash update?
WGTicon: sometimes, it's like you have 100000 threads in a roll and something changes inside, and you put on 1 thread and dont know what happens to the rest.
*nods* One small change can cause havoc (as we see on an hourly basis), that said if it is WGT fault, then I cant see why you cant role back your code and bisect the changes assuming you use a Concurrent Versions System.
I'm not saying that's a simple task that takes a matter of days, but this has been going on now for some time, as WGT are rolling out maintenance release's I'm guessing it must be a flash issue I just would like to know either way
Cheers
Ian