Not sure whats happening - but it seems like callStack problems may be the
culprit - looks like perhaps using XMLSocket would be a more reliable way to
go which is unfortunate...
On 5/16/06, Geoff Stearns [EMAIL PROTECTED] wrote:
maybe it's not serializing a value properly?
there are a few
Remember that this is a beta, so there are going to be issues.
We have recently fixed a bunch of issues with eternal interface
(including the ones mentioned by Geoff).
Do you have a simple reproduceable test case? If so, I can send it to
the team.
mike chambers
[EMAIL PROTECTED]
eric
Remember that this is a beta, so there are going to be issues.
We have recently fixed a bunch of issues with eternal interface
(including the ones mentioned by Geoff).
I've been also experiencing a lot of problems with Flash8
ExternalInterface, like the need to quote \\n to n in order to
We are working on a whitepaper to give Adobe SWF engineers - hope to have
something when we get a little time to put it together. It might boil down
to multi-threaded Python and single-threaded Flash (for the most part)... in
addition to some other things.
On 5/17/06, Mike Chambers [EMAIL
Its been called to my attention at work that sometimes my embedded SWF is
making calls out to Python (using ExternalInterface) where the XML document
only contains:
NaN/invoke
And thats it. Could this perhaps be a known bug in the player itself? The
syntax itself isn't valid.
maybe it's not serializing a value properly?
there are a few known issues with it in fp8, mainly newline elements...
more info here:
http://codinginparadise.org/weblog/2006/02/how-to-speed-up-flash-8s.html
On May 16, 2006, at 6:21 PM, eric dolecki wrote:
Its been called to my attention at
6 matches
Mail list logo
