Well, I don't have a dog in this fight with Macromedia.
For me, it's sort of like a very messy divorce. First there was love, then
angst, then anger, then the knock-down, drag-out.
Now I'm left dry, like a wrung-out dish rag too dry to wipe a counter top.
So, to push the metaphor a bit further, I send an alimony check to MACR more
from fear of reprisal than for hope of consideration, simply because the
reprisal is real and the consideration is nil. After the MX2004 debacle, the
sexiest offering gets only the most distant interest on my part; only the
most stridulant and screeching of client demands will force me to go into
that dark room and do that again. Thankfully those demands are few. Maybe
things will be different with "8-ball", but, once love is lost, it's hard to
get it back.
To solve your problem...I can't speak for the component in particular, but
components in general. When I'm in doubt of a component and find that I MUST
use it (and, I might add, it is immediately apparent that it is flawed
because it is not easy to use, nor is it flexible, and it requires radical
changes in the way I think or code, or, worst of all, it is too fat to fit
in my picture frame), I can generally find out quite a bit about it by
"dumping the object". This gives an alternate view from the actionscript
itself. For example, if you had a charting component called "myChart," you
could dump it as follows:
//where:
// sPre = string predecessor, used for spacing the trace commands
// idx = transient, multi-typed variable used as both an integer for
calculation and as an object for the object recursion
dumpObject(myChart, 0, "myChart");
function dumpObject (obj, nLevels, sName) {
var idx, sPre = '';
if (nLevels == null) {
nLevels = 0;
}
for (idx = 1; idx <= nLevels; idx++) {
sPre += '\t';
}
trace (sPre + sName + '{');
nLevels++;
for (idx in obj) {
if (typeof (obj[idx]) == 'object') {
dumpObject (obj[idx], nLevels, idx);
} else {
trace(sPre + idx + '=\"' + obj[idx] + '\"');
}
}
trace(sPre + '}');
}
Generally speaking this might help locating what the component is doing, its
functions, and what data it is looking for.
Hope this helps and isn't a redundancy or off target or something you've
already tried....BTW, I see that
www.blue-pac.com has got out a new charting
component set. I haven't tried it out, but I've found their technical
support superlative.
Good luck!
