With the last changes a new Bug apeared. If you add a XClip to stage, before its rendered, it will not apear after rendering. Please use onComplete-parameter (either with initialising the XClip or with renderAll(onComplete) ) to add the Clip and avoid that little prob. Currently theres no time to fix it on the fly, so  i also have to work with it.

After finishing my current pro-promo project, XClip v.1.0 priority will rise to nr. 1.

Anyway, have fun!

XClips was showing strange behavior, i detected after releasing the first versions. Now i’ve found the reason and Fixed it. The problem apeared whenever you’ve been working with many clips and global rendering controls: Some of the Clips still caused “core-supression” Errors, even after rendering was finished. Now that its Fixed, i release a new Package, v.0.9. There are some updates nessecary in the Docs, but that has to wait untill XClips will be stable. And i think, that i should remove the splice/append/insertFrames functions from the API, because i’m planing a kind of Composite-Timeline to the next version, to make work with many clips easy.

Now that i’m working a lot with the XClip to generate some impressive animations for my PromoSite, (will be found at www.opacki-flash.com), there are also a lot of improvments i do to the XClip, to become it stable.
Also meaning, that I will release better versions from time to time, when ever its worth it, but take notice that its beta, untill its not v.1.0 . XClips basic functionality will work anyway, you can prerender your animation, play/reverse/stop it and so on, but some complications might apear if you use many XClips in a more complex way, specialy if its about rendering-speed. So if you find something to report, please do it here, at the XClips blog.

XClips
RELEASE NOTES

*********************************************************
v. 0.9
*********************************************************

# IMPORTANT
Found a realy bad bug, that apeared, when many XClips where used with global rendering: renderAll(). Fixed.

# Different smal changes.
# Stable CoreSupressing.

*********************************************************
v. 0.8.2
*********************************************************

# IMPORTANT
There was a problem with coreSupressing, that caused different Errors right after rendering. Even if the renderer finished its work properly, clipCore access was still supressed in some case. Sorry. Fixed.

# clone(). Fixed.
# trace() calls. removed.
# Supressed Core Error Messaging. Fixed.
# Supressed ClipCore props access. Fixed.

*********************************************************
v. 0.8.3
*********************************************************

# IMPORTANT
Seems like alphaLoop and multiply cause errors, when used together. I’m sorry, please avoid that, until XClip has become stable.

# function reInit(). Integrated. Function is part of the API now, use it to delete mainpulations like alphaLoop or multiply. This function is experimental, please note that XClip is still in beta stadium.
# Compiler Warning. Removed.
# paramenter alphaOffset in multiply(). Removed, feature not yet integrated.
# some more clipCore-functions and props are now supressed, while rendering, to not cause null-object errors.

Action and Symbol are fast renderModes. Both of them create data in a for-loop. Complex rendering needs to preRender in realtime, meaning frame by frame, using the ENTER_FRAME Event. If you use frame-based tweens, its not a problem if the clients computer cant hold the frameRate, because all visible changes in your movie will be done frame by frame, the way they should be cached. Changes, based on time will cause jumping Clips, if the clients computer is a oldtimer or what you’ve created is a performance killer.

If you want to preRender less, low performance clips, you can make complex-rendering faster, by increasing your apps frameRate. This wont work, if your movie breaks the frameRate on the best CPU, but you should know that. This wont work with action- or symbol-rendering, because those modes create data in one frame and that takes time, depending of the clients CPU.