|
 |
 |
 |
 |
 |
| |
 |
After installation, components do not show up in Components panel. Why?
This problem has been experienced with CS3 flash editor. After you install a new ActionScript 2.0 component into Adobe Flash CS3, open Flash CS3 and create a new ActionScript 2.0 project, the newly installed component does not show up in the Components panel. First you need to check if your project is really published for ActionScript 2.0 – because if your project is set for ActionScript 3.0, some AS2 components might not show up. If this is not the case, then you probably encountered the problem described below.
It seems that Adobe Extension Manager 1.8 has a problem when installing Flash components for various language versions of Adobe Flash CS3. When the components are installed in the English version of Flash CS3, after installation they are displayed in the Components panel. This is not happening when Flash CS3 has a different language version (Spanish, Denmark, French, Japanese and so on).
In this case, the components are also installed but they do not show up in the Components panel because they are installed in the incorrect folder. It seems that the components are installed in the English configuration folder, regardless of the language version your copy of Flash CS3 is.
The solution to this problem is simply copy the newly installed files from the English configuration folder to your language configuration folder. For example, if the component you have just installed placed its .swc or .fla file in the Components folder or Libraries folder, you need to copy or move it from the English folder to your language folder. Also you need to copy or move Extensions folder with .mxi files from the English folder to your language folder.
Example for Windows systems:
Now, in case of Flash CS3 in a different language than English, you would have to copy or move all those files to the corresponding language configuration folder. For example, in case of the French version of Adobe Flash CS3, you would have to copy the contents of the
C:\Documents and Settings\user\Local Settings\Application Data\Adobe\Flash CS3\en\Configuration\Components
---> folder to --->
C:\Documents and Settings\user\Local Settings\Application Data\Adobe\Flash CS3\fr\Configuration\Components,
C:\Documents and Settings\user\Local Settings\Application Data\Adobe\Flash CS3\en\Configuration\Extensions
---> folder to --->
C:\Documents and Settings\user\Local Settings\Application Data\Adobe\Flash CS3\fr\Configuration\Extensions,
Also in case of buttons libraries, you would have to copy the
C:\Documents and Settings\user\Local Settings\Application Data\Adobe\Flash CS3\en\Configuration\Libraries
---> folder to --->
C:\Documents and Settings\user\Local Settings\Application Data\Adobe\Flash CS3\fr\Configuration\Libraries,
In case you have a different language version of Flash CS3, just replace the fr folder from the paths above, to the language folder you have.
Example for Mac OS systems:
Now, in case of Flash CS3 in a different language than English, you would have to copy or move all those files to the corresponding language configuration folder. For example, in case of the French version of Adobe Flash CS3, you would have to copy the contents of the
user/Library/Application Support/Adobe/Flash CS3/en/Configuration/Components
---> folder to --->
user/Library/Application Support/Adobe/Flash CS3/fr/Configuration/Components,
user/Library/Application Support/Adobe/Flash CS3/en/Configuration/Extensions
---> folder to --->
user/Library/Application Support/Adobe/Flash CS3/fr/Configuration/Extensions,
Also in case of buttons libraries, you would have to copy the
user/Library/Application Support/Adobe/Flash CS3/en/Configuration/Libraries
---> folder to --->
user/Library/Application Support/Adobe/Flash CS3/fr/Configuration/Libraries,
In case you have a different language version of Flash CS3, just replace the fr folder from the paths above, to the language folder you have.
Also this problem has been experienced with CS4 flash editor, if Operating Systems language differs from Flash CS4 language. Adobe Extension Manager 2.0 or higher has a problem when installing Flash components in the various language versions of Operating Systems for various language versions of Adobe Flash CS4.
Adobe Extension Manager has installed components in the incorrect folder -> Operating Systems language folder. The solution to this problem is simply copy the newly installed files from the Operating Systems language configuration folder to your Flash CS4 language configuration folder.
|
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
| |
 |
I have flash content on my site shows "Click to activate" message. Do you have any solution for it?
How to insert your flash menu on my web page correctly?
We recommend you to use the SWFObject. SWFObject is an easy-to-use and standards-friendly method to embed Flash content, which utilizes one small JavaScript file.
You can download SWFObject 2.2 here: You can download SWFObject HTML generator v1.2 (HTML version) here:
Embedding Adobe Flash Player content using SWFObject 2:
STEP 1: Create alternative content using standards compliant markup
SWFObject's dynamic embed method follows the principle of progressive enhancement and replaces alternative HTML content for Flash content when enough JavaScript and Flash plug-in support is available. First define your alternative content and label it with an id:
STEP 2: Include the SWFObject JavaScript library in the head of your HTML page
The SWFObject library consists of one external JavaScript file. SWFObject will be executed as soon as it is read and will perform all DOM manipulations as soon as the DOM is loaded - for all browsers that support this, like IE, Firefox, Safari and Opera 9+ - or otherwise as soon as the onload event fires:
STEP 3: Embed your SWF with JavaScript
swfobject.embedSWF(swfUrl, id, width, height, version, expressInstallSwfurl, flashvars, params, attributes, callbackFn) has five required and five optional arguments: - swfUrl (String, required) specifies the URL of your SWF
- id (String, required) specifies the id of the HTML element (containing your alternative content) you would like to have replaced by your Flash content
- width (String, required) specifies the width of your SWF
- height (String, required) specifies the height of your SWF
- version (String, required) specifies the Flash player version your SWF is published for (format is: "major.minor.release" or "major")
- expressInstallSwfurl (String, optional) specifies the URL of your express install SWF and activates . Please note that express install will only fire once (the first time that it is invoked), that it is only supported by Flash Player 6.0.65 or higher on Win or Mac platforms, and that it requires a minimal SWF size of 310x137px.
- flashvars (Object, optional) specifies your flashvars with name:value pairs
- params (Object, optional) specifies your nested object element params with name:value pairs
- attributes (Object, optional) specifies your object's attributes with name:value pairs
- callbackFn (JavaScript function, optional) can be used to define a callback function that is called on both success or failure of embedding a SWF file (see )
NOTE: You can omit the optional parameters, as long as you don't break the parameter order. If you don't want to use an optional parameter, but would like to use a following optional parameter, you can simply pass false as its value. For the flashvars, params and attributes JavaScript Objects, you can also pass an empty object instead: {}.
How can you configure your Flash content?
You can add the following often-used to the object element: You can use the following optional Flash specific param elements :
How do you use JavaScript Objects to define your flashvars, params and object's attributes?
You can best define JavaScript Objects using the Object literal notation, which looks like:
You can add your name:value pairs while you define an object (note: please make sure not to put a comma behind the last name:value pair inside an object)
Or add properties and values after its creation by using a dot notation:
Which can also be written as (the less readable shorthand version for the die-hard scripter who love one-liners):
If you don't want to use an optional argument you can define it as false or as an empty Object (NOTE: from SWFObject 2.1 onwards you can also use null or 0):
The flashvars Object is a shorthand notation that is there for your ease of use. You could potentially ignore it and specify your flashvars via the params Object:
the problem is solved!
|
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
|