Posted in Flash, Flex at 8:04 pm by Curtis J. Morley
Many of you probably already know but Flash Player 10 beta has just been released on Adobe Labs. This is a very exciting release of the player. Features include:
3D Effects - Easily transform and animate any display object through 3D space while retaining full interactivity. Fast, lightweight, and native 3D effects make motion that was previously reserved for expert users available to everyone. Complex effects are simple with APIs that extend what you already know.
Custom Filters and Effects - Create your own portable filters, blend modes, and fills using Adobe® Pixel Bender™, the same technology used for many After Effects CS3 filters. Shaders in Flash Player are about 1KB and can be scripted and animated at runtime.
Advanced Text Layout - A new, highly flexible text layout engine, co-existing with TextField, enables innovation in creating new text controls by providing low-level access to text offering right-to-left and vertical text layout, plus support for typographic elements like ligatures.
Enhanced Drawing API - Runtime drawing is easier and more powerful with re-styleable properties, 3D APIs, and a new way of drawing sophisticated shapes without having to code them line by line.
Visual Performance Improvements – Applications and videos will run smoother and faster with expanded use of hardware acceleration. By moving several visual processing tasks to the video card, the CPU is free to do more.
Thank you everyone for voting for my new logo. I had a great response. This is the winner. Using Google Analytics and Flash I was able to tell how many people voted, how many voted after viewing all the logos and how many people voted prematurely. I can tell how much time people spent on each logo, whether they preferred black-and-white or color and of course which logo was voted most liked among my readers. Look for the tutorial on how to do this with Flash/Flex coming soon.
ActionScript 3 Error #1061: Call to a possibly undefined method gotoAndStop through a reference with static type flash.display:DisplayObject.
ActionScript 3 Error #1061: Call to a possibly undefined method gotoAndStop through a reference with static type flash.display:DisplayObjectContainer.
ActionScript 3 Error #1061: Call to a possibly undefined method gotoAndStop through a reference with static type flash.display:Stage.
Description:
AS3 error 1061 will pop up when you trying to referencee an object from within a function that receives an Event. When you do this it will reference the DisplayObject or if you call out to this.parent rather than event.target.parent it will reference the DisplayObjectContainer which doesn't have a lot of methods with it.
Fix:
One solution to solve Flex/Flash Error 1061 is to make sure that you are using the event that is passed as the target by using
ActionScript Error #1151: A conflict exists with definition progBar in namespace internal.
ActionScript 3 Error #1151 Description:
AS3 error 1151 is an easy one. This means that within your ActionScript class(namespace internal) there is already a variable or function by that name.
Fix:
To solve Flex/Flash Error 11151 just hit CTRL-F(Apple-F) and search for that term that has a conflict and change it to something appropriate. You may have been building a particle system or working with an X or Y variable and forgot to change one of them so that they both read exactly the same. The example below shows what I mean and how to solve the issue.
Bad Code 1:
public class Particle extends Sprite
{
public var xVelocity:Number;
public var xVelocity:Number;
Good Code 1:
public class Particle extends Sprite
{
public var xVelocity:Number;
public var yVelocity:Number;
This should help you resolve Flash / Flex Error #1151
ActionScript 3 Compiler Error 1059 just means that you are trying to write to something that is read only. 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 Error is easy to understand and correct.
ActionScript Error 1059 Solution:The fix for Flex/Flash Error 1059 is to make sure that you are writing to writable property and not trying to write to a read only property. This is shown in two ways below.
Bad Code 1:
if(textName.length = 5)
Good Code 1:
if(textName.length == 5)
Bad Code 2:
var occurence:SharedObject = new SharedObject()occurence.data = "first";
Good Code 2:
var occurence:SharedObject = new SharedObject()occurence.data.whichTime = "first";
And now you know how to solve Flex /Flash Error 1059.
ActionScript Error #1118: Implicit coercion of a value with static type Object to a possibly unrelated type flash.display:DisplayObject
ActionScript Error #1118 can be caused by working with the Display Object. What happens is that as soon as you put a MovieClip, Sprite, etc... into the DisplayObject Flash/Flex thinks that any parent is of Type DisplayObject. Even though you know perfectly well that the object that contains your Sprite is another Sprite or MovieClip Flex and Flash don't know it. You may have encountered this Flex/Flash Error when you tried to call this.parent from within a Sprite or Flash MovieClip after using addChild() (among others) to display or modify the display of a MovieClip/Sprite on the stage. The compiler doesn't keep track of the Type that the parent is so when you call parent the compiler is confused. Instead it assigns the Type DisplayObject. Your code should still keep working even if you get this error, but there is a reason why the compiler gives you this error. I will show you how to get around this error and how to prevent yourself from getting this error in the future. This AS3 Error can happen any time that you are using any of the following methods:
addChild(); Adds a child DisplayObject instance to this DisplayObjectContainer instance.
addChildAt(); Adds a child DisplayObject instance to this DisplayObjectContainer instance.
contains(): Determines whether a display object is a child of a DisplayObjectContainer.
getChildAt(); Returns the child display object instance that exists at the specified index.
getChildByName(): Retrieves a display object by name.
getChildIndex(): Returns the index position of a display object.
setChildIndex(): Changes the position of a child display object.
<code>swapChildren(): Swaps the front-to-back order of two display objects.
<code>swapChildrenAt(): Swaps the front-to-back order of two display objects, specified by their index values.
Another reason you may get this ActionScript3 Error is by having an external class that is assigned to an object at runtime. Because the class is not predetermined therefore the compiler chokes.
AS3 Error #1118 Solution. You can resolve AS3 Error #1118 by doing one of three things. The first and most highly suggested is to change the way you code. Think from an outside-in perspective when coding rather than an inside-out mentality. The second is to cast the object as the proper Type which explicitly tells the compiler the type of the parent. The third is to just turn off verbose comments in your settings. I don't suggest doing this last fix as it could lead to many more headaches and is horrible when working with a team.
AS3 Error 1118: Fix #1 - Object Oriented Scripting. Code with an outside-in perspective. This means that instead of the child telling the parent what to do the parent tells the child what to do. This may become tricky if you are completing an animation and need an event to happen when the inner movieClip reaches a certain frame. It is still possible and I may post a tutorial on how to do this with Flash in the near future. But this post is not the right place for it. You can pick up Essential ActionsCript 3 by Collin Moock for a great reference and starting point.
AS3 Error 1118: Fix #2 - Cast the object as the type that you know it is. If you know that it is a MovieClip then tell Flash that it is a MovieClip. You do this by Casting the object as shown below.
Bad Code:
this.parent.doSomething();
Good Code:
MovieClip(this.parent).doSomething();
or
(this.parent as MovieClip).doSomething();
AS3 Error 1118: Fix #3 - *Warning* This method will solve the problem temporarily and allow you to publish your code BUT it will cause you many headaches later. You will not get any warnings or error messages and this is a bad thing I Promise! If you are going to proceed down this path make sure to recheck these boxes after you are done publishing your one problem movie. With that much said, The way you do this is to turn off Strict (Verbose) Error Messages in your preferences as shown below.
Go to File >> Publish Settings >> Click on the "Flash" tab >> Next to "ActionScript version:" click the "Settings..."
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 for your help in picking a new logo for my site. This experiment is a follow-on to my posts about integrating Google Anayltics and Flash. Thanks to Clint Rogers for the opportunity to present my findings at BYU on March 27, 2008. There are many things to consider when considering how to Integrate Flash and Google Analytics. With your help I can test my assumptions. This will gather data and tally votes using nothing more than Google Analytics.
I want to give a special thanks to my friend and fantastic designer Larry Lee Lentz II for his help on these logos and design.
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
ActionScript 3 Error #1120: Access of undefined property myButton_btn.
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.
Fix1:
Give your instance the proper instance name
Bad Example:
Good Example:
Fix2:
Check that your reference is the proper instance name Bad Code:
by Collin Moock for a great reference and starting point.
