> I was under the impression that you were asking about a static object that does not have any keyframe animation applied to it.
That was true of my simple image-swap test. Ultimately the image-to-be-replaced will translate a little, but always return to a starting point. Some time later that stops, and javascript swaps in a new IMG -- at the starting point. So it does work to use the x & y IMG position values from the IDE, hokey though that may be, because they persist throughout.
> Translate3d is not a css property. You will need to retrieve the string in css transform (or webkitTransform) property and then parse the string to get the translate3d parameters.
Yes, i was prepared to extract the IMG x & y position from translate3d values in the DOM because it works when i put them there.
If i replace the image like this:
var target_div = controller.getElementById('id');
// traverse to IMG node
// parentNode.removeChild(found_img);
// parentNode.appendChild(new_img);
target_node.style.webkitTransform = "translate3d(335px,54px,0px)";
… then the new image is positioned correctly. If I skip that last line, the image is positioned at browser top left.
And given translate3d() positioning, you can find it in the DOM:
outerHTML
"<img id="sym-catfish" src="assets/slot_sym15.jpg" alt="catfish" style="-webkit-transform: translate3d(335px, 54px, 0px);">"
style. cssText
"-webkit-transform: translate3d(335px, 54px, 0px);"
style.webkitTransform
"translate3d(335px, 54px, 0px)"
I thought you guys were doing much the same, in which case the translate3d values ought to be in there somewhere.
Thanks again for all your help and insight. The flexible layout information looks to be particularly valuable, although I’m not quite there yet. In fact my little image swap test was done on Animator 1.3.
But I’m looking forward to the adventure.
~Paul