This content has been marked as final. Show 3 replies
gwd told me to tell you that it's due to a stray kryptonite instance. On a more serious note, I guess it's safe to assume the URL to the library is correct, and the swf isn't being moved around between publishes...?..
That is exactly what I was thinking!
Actually I wasn't quite accurate. It isn't exported for runtime sharing, but perhaps it should be? I didn't set this up.
We have an external fla called SharedObjects (I know bad name, but that is what it is!) and it has all these little interface elements and other bits and bobs. They are all placed on the stage in a MovieClip called SharedObjects.
Then we open our production FLA, open the SharedObject FLA as an external library, drag over the SharedObject movie into our production library. We then go into the properties and check Source "Always update before publishing."
We have two different sets of this. One that has all the interface bits and one that has a bunch of bits that our development environment uses. For some odd reason if the Border is in the first FLA it only works every other publish. If I put it into the SharedObjectDev FLA it works fine.
And you are correct there is nothing moving between publishes. Nothing being saved, saved and compacted, or anything. Just publish, close test environment, publish. (I have tried combinations of saving, compacting, etc. and it makes no difference.)
I don't know how to use the export for runtime sharing. Is that more reliable? Should I look into it?
Kirupa has a nice tut on a true shared library. Here she is.
"We then go into the properties and check Source "Always update before publishing.""
I've never heard of this method, lol, sounds kinda make-shift.
Come by the forum in my sig and jump on live support so you can have a little chat with gwd lol. I know he's dying to explain more about the kryptonite instance, which he swears by.