It looks like currently you are only allowed to see the Application states, and the componenet states of anything that is currently nested within your custom component.

The problem that I have is that when a button is pressed within component 1, I want to not only change the Application State, but I want to adjust the state of component 2 (not nested in component 1) based on the button pressed.

If we were allowed to see all of the components (and their states) when using the Interactions Panel, this would solve this issue.

Thanks!

Nick

Well the title says it all. This would make the workflow go so much faster! Having to recreate a set of transitions for each navigation button on each page takes forever. For example: A very small website could have 5 buttons on 5 pages. This means having to recreate the transition 25 times! For a SMALL site... Sorry guys, but "Smooth Transition" is worthless for this!

I'm not sure I can explain this generically, so here is a case example:

The HUD forsees having buttons for GO TO "state" WHEN IN "state".

I am building step-through animations with, for example, step1, step2 .... step9 buttons for each state. My viewer, who doesn't know FC, is thinking in terms of actions, not states. Let's say he has just viewed the transition between state3 and state4. I would like to allow him to repeat the motion sequence he's just seen - by using a replay button located in state4.

This would mean having something like GO TO "this state" USING TRANSITION FROM "stateX(previous state)" in the HUD.

Don't know if it's do-able and it's only relevant for sequential presentations, so please comment if this is of general interest.

It would be cool if when adding interactions to a component, you could have more than one "When In" conditions.

I'd like the ability to maintain interactions when copying Custom Components. For example, if I copy and paste a Custom Component, or if I export it to a components library and then import it, it loses all of its defined interactions. This requires me to re-assign them one-by-one which can be incredibly tedious.