This content has been marked as final. Show 6 replies
I think you should keep your graphics in cost and call them when required and try to use containers for example if there are too many text boxes, fields try to change just values from cast instead of placing them on stage
Split your movie into parts
I know its very poor solution but i wish to share with you may be it help you
Best of luck,
The best bet is to just put together a lot of your graphics on the fly with imaging lingo. That way many things can all sit in one sprite.
Depending on what you are doing, you could also consider using LDMs (Linked Director Movies), or Flash sprites.
The plan has more than 250 workorders that shall be produced on 5 workcenters. Each WO on the plan should be selectable. I cannot see that this can be done any other way? This is a web-application, Shockwaved. What can be done with Flash sprites?
"LINiLund" <firstname.lastname@example.org> wrote in message
> The plan has more than 250 workorders that shall be produced on 5
> Each WO on the plan should be selectable. I cannot see that this can be
> any other way? This is a web-application, Shockwaved. What can be done
> Flash sprites?
if you really need to have 1000 sprites on the stage all at once, then I
think your approach is maybe wrong.
For users it is probably impossible to handle all that info, and for you it
is not possible to get it all on the stage, readable, understandable and
How do you manage to keep track of those 1000 sprites yourself BTW?
Why not use a sort of pagination-method, or a master-details approach?
What is in the sprites? Text? Graphics? Can you not reorganise the info?
You can use Film Loops and Linked Director Movies to nest sprite channels. Here's an article I wrote back in the days of Director 5, when there were only 48 channels (I was creating a music score editor, and needed a sprite for each note): http://director-online.com/buildArticle.php?id=154
Linked Director Movies are more powerful than film loops, but require that the movie be stored externally.
I totally agree...1000 sprites should never be needed.
With a Flash sprite you can easily communicate with Director, so sometimes it is easier to build something in Flash that will dynamically create a lot of things inside it.
To see what can be done with single sprites using imaging lingo you may want to check out the One Sprite Widgets