deleting components

[rbwrath]

i'm new to actionscript and ran into a problem with a deleted component.

I read another thread somewhere that said that deleting components will really mess with the program, and i believe it suggested that you keep all the other components on another depth to keep them from conflicting.

right now what is happening is, i have 2 comboboxes created in the actionscript, and I was having an initial problem with depth and made a test combobox to figure out what was wrong. unfortunately after i deleted the test cbox, it reappears(in the flash movie) whenever i leave the frame and come back to it. it also makes the original 2 cboxes disappear. i tried changing the depths for all the components in the file, but it still does what it does.

any help would be greatly appreciated

[dvlnblk]

i'm new to actionscript and ran into a problem with a deleted component.

I read another thread somewhere that said that deleting components will really mess with the program, and i believe it suggested that you keep all the other components on another depth to keep them from conflicting.

right now what is happening is, i have 2 comboboxes created in the actionscript, and I was having an initial problem with depth and made a test combobox to figure out what was wrong. unfortunately after i deleted the test cbox, it reappears(in the flash movie) whenever i leave the frame and come back to it. it also makes the original 2 cboxes disappear. i tried changing the depths for all the components in the file, but it still does what it does.

any help would be greatly appreciated

This is just another reason why I, and many other Flash professionals advocate not using components. But, as for your problem try clicking File>save and compact. That might help your problem. Dvl

[Sleeve]

This is just another reason why I, and many other Flash professionals advocate not using components...

This is just another reason why you and many other flash professionals need to understand components in the first place. Or build your own :P

I formed a deep respect for components after going though the ComboBox Class line by line trying to understand it's logic.

Afterwards, I coded my own and came close to the built in component after 1500+ lines of code.

[dvlnblk]

Your answer just makes me think that YOU are not a Flash professional. : P

For the same reason that you stated is one of the reasons why they are bad, the amount of code in them is rediculous. If you use one component you are getting the code for ALL components. Also, another major reason is they are not skinable, why in the heck would anyone want to use Flash instead of HTML? ANSWER: you want it to look better, different from HTML, amimate.

Trust me, your better off building your own objects as needed and store them in your own library. If you still need more proof check these links out:

http://board.flashkit.com/board/archive/index.php/t-563308.html

http://www.actionscript.org/forums/showthread.php3?t=47481

http://www.northcode.com/forums/archive/index.php?t-4131.html

Do your own research and I think you might change your mind.

Dvl

http://flashmove.com/forum/showthread.php?t=14687

http://tim.2wgroup.com/blog/archives/000786.html

[Sleeve]

Whoa chill buddy. I don't need proof because I know.. (Components ARE skinnable BTW - http://www.adobe.com/devnet/flash/articles/skinning_2004.html) If you know the reasons Macromedia made components the way they are is because their research concluded that MOST people who use components will have 3 or more of them in their app.

If components use Classes that are shared, your filesize actually goes DOWN. You can test it yourself - Drag 10 V1 components on stage, compile the movie and note it's size. Do the same for V2 components and note it's size. The 10 V2 components are much, much smaller than the V1 components.

Sure, build them yourself. I do it from time-to-time but development time goes way up when you do that unless you frankestein your code.

Besides, show me a component that you've built that has 1/10 the functionality of a V2 component and uses proper coding technique...Captian

[dvlnblk]

I guess then you should go on building sites that use components but I, for one, choose to build class A sites that have no need for them. If you would like a list of sites that I have made without them then I am willing to provide them. And, my clients have specs on k size that are very strict. But if they work for you, then use them but as for me I think they are not good and not good insofar as good practices go. Good luck, I DO mean that. Dvl

[dvlnblk]

And just so you understand, I use macromedia dreamweaver, but I don't use the Split or Design mode because I can make it better in the Code mode. This is the same thing to me. Just trying to clarify and not offend. Dvl