So I placed one image exhibit on State 1. I then made it a custom component.
I edited the custom component and create additional States within the component. On one of those States I added a roll-over.
All of it worked.
My question is what’s the difference in performance if I am still going to add 200 odd exhibits in Custom Component States vs. the main application states?
Will I run into any performance issues?
What am I missing or mistakes should I avoid.
Again, thanks for any help.
My advise would be to break it down.
For example on a web-site, one might have 5 pages, you could also have a few catalyst sites...
But if not, don't fret.
You have an option on the images to have them outside of your actual catalyst project (linked) or embedded. Embedded will take longer load times, up front, but liked images will load on activation or presence in a state. Good practice might be to make all front-page images and a few time-sensitive images embedded, simply so everything starts at the same moment. Otherwise, you can do lists (google and look for ordered lists) or other ways of managing the images.
Note that 'buttons' can reveal images etc, like a slide-show, it doesn't HAVE to be based on 'states'. Also, again, you can have several catalyst projects and link the two creatively to do some more with it all... this would be for a hosted site, no?
In the beginning especially, parse it down or come with a strategy. What I find annoying is not realizing little steps and having to repeat them, I imagine the software will start to get some steroids soon, but for now, poke around maybe with beginners book.
If you are using vector art you can do a lot to optimize it in the layers panels, losing the strike/fill sublayers, which makes them once piece, and this also cuts load time. Optimizing graphics is one thing that can help a lot, and you can do that with the fly-out obviously. These things are small compared to how you host the images (embedded vs. linked).
Does this help?