Do component properties applied in a FLA need to be activated in AS3?
up vote
-1
down vote
favorite
I'm trying to make my Buttons and ComboBoxes work with custom component properties in Adobe Animate CC (also tried on CS6) and I swear, I'm going to have an aneurysm. I've looked everywhere on the internet and can't find the answer to this question: do component properties defined in a FLA document need to be activated somehow in either AS3 or elsewhere?
Here's what my MovieClip looks like in the FLA (notice how the buttons and dropdown have custom text):
This is what it actually looks like (notice none of my custom settings have saved):
I've filled out the component properties in the FLA file, so the only other thing I can think of is I need to apply or import the settings somehow in AS3. If anyone can provide some insight, please weigh in. Cheers, thank you.
actionscript-3 flash components adobe flash-cs6
asked Nov 20 at 10:03
bls1999
273
add a comment |
up vote
-1
down vote
favorite
I'm trying to make my Buttons and ComboBoxes work with custom component properties in Adobe Animate CC (also tried on CS6) and I swear, I'm going to have an aneurysm. I've looked everywhere on the internet and can't find the answer to this question: do component properties defined in a FLA document need to be activated somehow in either AS3 or elsewhere?
Here's what my MovieClip looks like in the FLA (notice how the buttons and dropdown have custom text):
This is what it actually looks like (notice none of my custom settings have saved):
I've filled out the component properties in the FLA file, so the only other thing I can think of is I need to apply or import the settings somehow in AS3. If anyone can provide some insight, please weigh in. Cheers, thank you.
actionscript-3 flash components adobe flash-cs6
asked Nov 20 at 10:03
bls1999
273
1
No, normally they don't need any "activation". You, again, normally, do it WYSIWYG style: you fill the component fields in Flash IDE and they get published as it.
– Organis
Nov 20 at 10:49
That's what I thought. Do you know what I could be doing wrong?
– bls1999
Nov 20 at 19:48
A wild guess. Well, the most common case of component malfunctioning. When you add one to your project, it automatically adds all its dependencies to the project's Library. But then it has no compile time or runtime control. Thus, if anything gets to happen to its pieces (like, you accidentally remove one piece from the Library), you might not even get any errors, but the component won't function or will malfunction in a number of possible ways.
– Organis
Nov 20 at 20:08
Gotta love flash, lol. I did some debugging and found that if I put components on the main timeline (not a movieclip) they work. Seeing as I'd already wasted two days trying to figure out why the components wouldn't work anywhere, I considered this a win and just resorted to setting the properties via AS3.
– bls1999
Nov 21 at 5:46
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I'm trying to make my Buttons and ComboBoxes work with custom component properties in Adobe Animate CC (also tried on CS6) and I swear, I'm going to have an aneurysm. I've looked everywhere on the internet and can't find the answer to this question: do component properties defined in a FLA document need to be activated somehow in either AS3 or elsewhere?
Here's what my MovieClip looks like in the FLA (notice how the buttons and dropdown have custom text):
This is what it actually looks like (notice none of my custom settings have saved):
I've filled out the component properties in the FLA file, so the only other thing I can think of is I need to apply or import the settings somehow in AS3. If anyone can provide some insight, please weigh in. Cheers, thank you.
actionscript-3 flash components adobe flash-cs6
asked Nov 20 at 10:03
bls1999
273
I'm trying to make my Buttons and ComboBoxes work with custom component properties in Adobe Animate CC (also tried on CS6) and I swear, I'm going to have an aneurysm. I've looked everywhere on the internet and can't find the answer to this question: do component properties defined in a FLA document need to be activated somehow in either AS3 or elsewhere?
Here's what my MovieClip looks like in the FLA (notice how the buttons and dropdown have custom text):
This is what it actually looks like (notice none of my custom settings have saved):
I've filled out the component properties in the FLA file, so the only other thing I can think of is I need to apply or import the settings somehow in AS3. If anyone can provide some insight, please weigh in. Cheers, thank you.
actionscript-3 flash components adobe flash-cs6
actionscript-3 flash components adobe flash-cs6
asked Nov 20 at 10:03
bls1999
273
asked Nov 20 at 10:03
bls1999
273
edited Nov 20 at 10:10
asked Nov 20 at 10:03
bls1999
273
asked Nov 20 at 10:03
bls1999
273
asked Nov 20 at 10:03
bls1999
273
273
1
No, normally they don't need any "activation". You, again, normally, do it WYSIWYG style: you fill the component fields in Flash IDE and they get published as it.
– Organis
Nov 20 at 10:49
That's what I thought. Do you know what I could be doing wrong?
– bls1999
Nov 20 at 19:48
A wild guess. Well, the most common case of component malfunctioning. When you add one to your project, it automatically adds all its dependencies to the project's Library. But then it has no compile time or runtime control. Thus, if anything gets to happen to its pieces (like, you accidentally remove one piece from the Library), you might not even get any errors, but the component won't function or will malfunction in a number of possible ways.
– Organis
Nov 20 at 20:08
Gotta love flash, lol. I did some debugging and found that if I put components on the main timeline (not a movieclip) they work. Seeing as I'd already wasted two days trying to figure out why the components wouldn't work anywhere, I considered this a win and just resorted to setting the properties via AS3.
– bls1999
Nov 21 at 5:46
add a comment |
1
No, normally they don't need any "activation". You, again, normally, do it WYSIWYG style: you fill the component fields in Flash IDE and they get published as it.
– Organis
Nov 20 at 10:49
That's what I thought. Do you know what I could be doing wrong?
– bls1999
Nov 20 at 19:48
A wild guess. Well, the most common case of component malfunctioning. When you add one to your project, it automatically adds all its dependencies to the project's Library. But then it has no compile time or runtime control. Thus, if anything gets to happen to its pieces (like, you accidentally remove one piece from the Library), you might not even get any errors, but the component won't function or will malfunction in a number of possible ways.
– Organis
Nov 20 at 20:08
Gotta love flash, lol. I did some debugging and found that if I put components on the main timeline (not a movieclip) they work. Seeing as I'd already wasted two days trying to figure out why the components wouldn't work anywhere, I considered this a win and just resorted to setting the properties via AS3.
– bls1999
Nov 21 at 5:46
1
1
No, normally they don't need any "activation". You, again, normally, do it WYSIWYG style: you fill the component fields in Flash IDE and they get published as it.
– Organis
Nov 20 at 10:49
No, normally they don't need any "activation". You, again, normally, do it WYSIWYG style: you fill the component fields in Flash IDE and they get published as it.
– Organis
Nov 20 at 10:49
That's what I thought. Do you know what I could be doing wrong?
– bls1999
Nov 20 at 19:48
That's what I thought. Do you know what I could be doing wrong?
– bls1999
Nov 20 at 19:48
A wild guess. Well, the most common case of component malfunctioning. When you add one to your project, it automatically adds all its dependencies to the project's Library. But then it has no compile time or runtime control. Thus, if anything gets to happen to its pieces (like, you accidentally remove one piece from the Library), you might not even get any errors, but the component won't function or will malfunction in a number of possible ways.
– Organis
Nov 20 at 20:08
A wild guess. Well, the most common case of component malfunctioning. When you add one to your project, it automatically adds all its dependencies to the project's Library. But then it has no compile time or runtime control. Thus, if anything gets to happen to its pieces (like, you accidentally remove one piece from the Library), you might not even get any errors, but the component won't function or will malfunction in a number of possible ways.
– Organis
Nov 20 at 20:08
Gotta love flash, lol. I did some debugging and found that if I put components on the main timeline (not a movieclip) they work. Seeing as I'd already wasted two days trying to figure out why the components wouldn't work anywhere, I considered this a win and just resorted to setting the properties via AS3.
– bls1999
Nov 21 at 5:46
Gotta love flash, lol. I did some debugging and found that if I put components on the main timeline (not a movieclip) they work. Seeing as I'd already wasted two days trying to figure out why the components wouldn't work anywhere, I considered this a win and just resorted to setting the properties via AS3.
– bls1999
Nov 21 at 5:46
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390508%2fdo-component-properties-applied-in-a-fla-need-to-be-activated-in-as3%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
No, normally they don't need any "activation". You, again, normally, do it WYSIWYG style: you fill the component fields in Flash IDE and they get published as it.
– Organis
Nov 20 at 10:49
That's what I thought. Do you know what I could be doing wrong?
– bls1999
Nov 20 at 19:48
A wild guess. Well, the most common case of component malfunctioning. When you add one to your project, it automatically adds all its dependencies to the project's Library. But then it has no compile time or runtime control. Thus, if anything gets to happen to its pieces (like, you accidentally remove one piece from the Library), you might not even get any errors, but the component won't function or will malfunction in a number of possible ways.
– Organis
Nov 20 at 20:08
Gotta love flash, lol. I did some debugging and found that if I put components on the main timeline (not a movieclip) they work. Seeing as I'd already wasted two days trying to figure out why the components wouldn't work anywhere, I considered this a win and just resorted to setting the properties via AS3.
– bls1999
Nov 21 at 5:46