I am going to post every day this month. Most posts with be ActionScript Errors but I will also include tutorials and Flash SEO and Google Analytics reports and info. Sometimes just for kicks I will throw in some marketing and random thoughts. So look for daily post in May.
FYI – Because Sunday is a special day for me I will not be posting on Sundays but will make up for that on other days.
Thanks and Happy Flashing
Curtis J. Morley
ActionScript Error #1024: Overriding a function that is not marked for override.
Description:
AS3 error 1024 means that Flash or Flex already has a function by that name.
Fix:
To solve Flex/Flash Error 1024 all you need to do is either correctly name the function something besides a reserved function in Flex/Flash or properly override the function. The example below shows how to solve issue number one. Notice that the good code solves Error 1024 because it doesn’t use the same name as a function that already exists in ActionScript.
Bad Code 1:
function nextFrame (e:MouseEvent):void
{
this.nextFrame();
}
Good Code 1:
function onNextFrame (e:MouseEvent):void
{
this.nextFrame();
}
This should help you resolve Flash / Flex Error #1024
Thanks and as always Happy Flashing
Curtis J. Morley
Description:
ActionScript error #1120 means that an object “property” within Flash or Flex is not defined. But this doesn’t really help you fix it. One main reason for this AS3 Error is that you haven’t given the MovieClip or Button an instance name when you placed it on the stage in Flash. Another reason is that the reference is not correct.
AS3 Error 1120 –Fix1:
Give your instances a proper instance name.
Bad Example:
Good Example:
AS3 Error 1120 –Fix2:
Check that your reference is the proper instance name.
Bad Code:
myBatton_btn.addEventListener(MouseEvent.CLICK, someFunction);
Good Code:
myButton_btn.addEventListener(MouseEvent.CLICK, someFunction);
AS3 Error 1120 – Fix3:
Make sure that you are calling the function with the correct name.
Bad Code:
square.addEventListener(TouchEvent.TOUCH_BEGIN, touchBeginHandler);
function fl_TouchBeginHandler(event:TouchEvent):void
{
//Drag something
}
Good Code:
square.addEventListener(TouchEvent.TOUCH_BEGIN, touchBeginHandler);
function touchBeginHandler(event:TouchEvent):void
{
//Drag something
}
As Always, Happy Flashing
Curtis J Morley
Warning: 1100: Assignment within conditional. Did you mean == instead of =?
Description:
AS3 warning 1100 is Adobe watching out for you and helping you out. Flash/Flex let’s you know that you are assigning a variable while at the same time evaluating to see if it is true. This AS3 warning is quite easy to understand and well written.
Fix:
To solve Flex/Flash Warning 1100 all you need to do is add another ” = ” sign inside your conditional making 2 == rather than just one.
Bad Code 1:
if (topFive[i]=“one”) {
Good Code 1:
if (topFive[i]==”one”) {
Note: This is not ActionScript Error #1100. Click this link to find AS3 Error #1100.
This should help you resolve Flash / Flex Warning #1100
Thanks and as always Happy Flashing
Curtis J. Morley
Added a code example to AS3 Error # 1176 and cleaned up the formatting for your viewing pleasure.
Get the updated info on ActionScript Error #1176 here.
Thanks and Happy Flashing
ActionScript Error #1065: Variable MyClassName is not defined.
Description:
This ActionScript error means that Flash or Flex does not understand the definition of your Class. One reason for this is that you forgot to declare your class as public. Another reason is that the reference is not correct. Don’t be deceived by the word Variable in this error it is really a class.
Fix:
Add public before the name of your class.
Bad Code:
class MyClassName extends MovieClip
Good Code:
public class MyClassName extends MovieClip
Fix 2:
Correctly reference the class that is being used.
Good luck trouble shooting ActionScript Error #1065 and,
As always Happy Flashing
ActionScript Error #1094: Syntax error: A string literal must be terminated before the line break.
Description:
Error 1094 is a simple and fairly well described ActionScript Error. This error will appear when you have left off the closing single quote marks in a particular line. This is very closely related to AS3 Error 1095 which will help you out when you improperly use double quotes. You will most likely get AS3 syntax error 1083 and syntax error 1084 after this this one. These can most likely be ignored and will go away once the 1094 error is taken care of
Fix:
End the string properly by putting double quotes in the proper place
Bad Code:
trace(‘This is missing a single quote + someVar);
Good Code:
trace(‘This is not missing a single quote’+ someVar);
Related ActionScript Errors – AS3 Error 1095, AS3 Error 1084
This ActionScript Error is a quick one. I hope this helps you solve it.
As always Happy Flashing
I’ve added 3 new scenarios to AS3 error 1084.
You can find it here.
http://curtismorley.com/2007/07/14/flash-cs3-flex-2-error-1084/#comment-2482
The additions are:
1084: Syntax error: expecting leftparen before colon.
1084: Syntax error: expecting rightparen before colon.
1084: Syntax error: expecting rightparen before semicolon.
ActionScript Warning: 3551: Appending text to a TextField using += is many times slower than using the TextField.appendText() method.
ActionScript Error Description:
I love this ActionScript Warning. This is not technically an ActionScript Error instead it is a warning that helps you code better. It is very clear and easily deciphered. This states that you should not use the old way to add text to a text field but rather use the new TextField.appendText() method. This improves performance dramatically and will prevent the user from getting the 15 sec. timeout. (Error #1502: A script has executed for longer than the default timeout period of 15 seconds.)
Fix:
Use TextField.appendText() instead of +=.
Bad Code:
var something:String = “Happy “;
var somethingElse:String = “Birthday”;
myTF_txt.text = something;
myTF_txt.text += somethingElse;
Good Code:
var something:String = “Happy “;
var somethingElse:String = “Birthday”;
myTF_txt.text = something;
myTF_txt.appendText(somethingElse);
ActionScript Warning #3551 is simple and easy (the way that all ActionScript errors/ warnings should be)
As always – Happy Flashing
ActionScript Error #1150: The protected attribute may be used only on class property definitions.
Description:
This ActionScript Error justs means that you have used the access control modifier ‘protected’ in the wrong spot. There are four access control modifiers – public, private, internal, and protected. Each of these specify how the method or variable is accessed. Each access control modifier has it’s own error but they all mean the same thing. Access control modifiers need to be used in the right place. The ‘internal’ and ‘public’ can only be used inside a ‘package’ and ‘private’ and ‘protected’ can only be used on classes.
Fix:
Make sure to only use the ‘protected’ access control modifier to define a method or variable within the class itself and not within a method(function).
Bad Code:
package{public class MySize {public function Connection():void{protected var borderSize:uint = 0;trace(size);}}}
Good Code:
package{public class MySize {private var size:uint = 40;protected function Connection():void{trace(size);}}}
Related ActionScript Errors – AS3 Error 1013, AS3 Error 1114, AS3 Error 1115
This ActionScript Error is a quick one. I hope this helps you solve it.
As always Happy Flashing
