How is the code slightly off? By using the onClick with the "when in " " state" you should be able to get what you need. It is the designers shortcut to the "if-then" that a programmer would do.
>>>using the onClick with the "when in " " state"
That's what I said I was currently doing, in my post. What I was asking is, if that's the best way to accomplish it. If I have 100 images and 100 transitions, it's going to get messy.
Creating separate transitions seems more like brute force rather than elegance and I can't imagine a programmer wanting to see all those transitions.
As far as the 'slightly off' statement, I just meant that the product is a bit buggy and that's expected, so it caused me to wonder if I was even taking the right approach. If it's the only approach then it's the right one, but I don't know, so's I'm askin.
As I was typing in my original post, it began to dawn on me that my view of FC may be skewed. I mentioned that I was hoping FC would enable the individual user (e.g. freelancer) to develop UI's for real world use, without learning AS3, but that may not be the case at all. If we need to learn Flash Builder to accomplish that, then I should probably get back to learning AS3.
I've been a programmer for 25 years, but AS3 has been kicking my butt for 6 months. I'm trying to get away from programming to create art, but the programmer in me can't hand off the task off to someone else (much less be able to afford it.)
A boy can dream....
Hi there--in the current version of FC, using states, transitions and interactions as you're doing is the primary method we have for building what you're trying to build. Over time, we'd like to add more ability to "generalize" parts of your design so that they can be reused without manually managing all the individual cases--Data Lists are a first example of this, though in their current form they don't solve your use case.
We've also gotten a lot of feedback on timeline management and are looking at ways to make it easier to manage multiple timelines and effects.