- Has been a member for 3-4 years
- Exclusive Author
- Sold between 10 000 and 50 000 dollars
- Bought between 1 and 9 items
nice
nice
Cool stuff! 
The purpose of a Flash component is to encapsulate all functionality and associated assets within a compiled movie-clip, while making implementation easy on the end user by leveraging the component inspector for setting various parameters and values. This, very poorly developed file does none of these things but does serve as a shining example of what not to do when developing a Flash component. Before purchase, pay particular attention to the ReadMe statement: “Don’t REMOVE contents from the movieclips.” What this essentially means is, if you want to use this component within your project, you need to have the nine or so button instances on stage with an alpha value of zero in order for this thing to actually work- ie: the developer has coded this component assuming the presence of these instances. This is not appropriate as this can only serve to increase file-size, especially if I’m not planning on using them in any capacity whatsoever. Super lame- I want my $8 back.
It suddenly dawned on me that with “don’t remove movieclips” you may have meant the component itself. But actually that means the movieclip assets inside frame 2 of the component itself. Obviously you can remove the component from the Library. And with that you by the way emphasize my point about non-compiled components -> It does not export-in-first-frame so if at any point you choose not to use it and not delete it from Library, it will NOT increase files size, which compiled clips with common export-in-first frame do.
Anyhow, if you need assistance, email me directly
Fantastic component. Really easy to implement a great firework show. Thanks for a really nice, top quality, professional component.
there is a 3 second wait before the fireworks begin. is there a way of immediately launching this? none of the parameter settings seem to address that. i tried “min. start delay” but it’s probably the wrong setting. maybe tweak the AS code? thanks.
COPYRIGHT © 2012 ENVATO| TERMS OF USAGE| SUPPORT/HELP| ICONS BY TANGO + WEFUNCTION + FAMFAMFAM
Adobe®, Flash®, Flex®, Fireworks®, Photoshop®, Illustrator®, InDesign® and After Effects® are registered trademarks of Adobe Systems Incorporated.
Sorry to hear you’re not satisfied so far. But I probably could have helped out, as I usually do insofar as I can, to facilitate adjustments to your/customers needs, if you had contacted me directly per email. And of course that offer still and will always stay as such, no offense taken
About components, I’ve been almost doing that solely since around 2002 in compiled and non-compile forms, and I can safely tell you that the purpose is not nessesarily to always close-compile contents, that only makes them partly not editable. The amount of editability I leave open varies depending on the specific item, and I’m actually un-”compiled-clip”-ing a number of them for reupload on FD.
In this particular item, it does offer all nessesary component parameters in Inspector, as shown on preview image, and leaves scripting in compiled form. The ‘don’t remove contents’ makes complete sense since removing any from within the component will leave it non-funcional. About the need to have the nine buttons on stage, that’s not correct, you merely need to select “export in first” frame property to avoid that. Which is not default since assets and SHIM are placed on component second keyframe, as adobe documentations will explain will make them available for component funcionality when you drag them on stage. Exactly for this reason you do NOT need to have them on stage as you mentioned, as well as why this is the same reason it will NOT increase file size nessesarily.
Once more, I do regret you’re not happy with it so far and you can always contact me for the non-compiled form or request changes made. About refunds you’ll have to contact FD and see what options your have.