Here’s the code sample that was included in the aforementioned tutorial:

if (result == null) {
//do nothing
} else {
//use the value of result to proceed with the script
}

This example reflects code for custom XMLUI panel, but this technique can also be used for alerts, prompts, and confirmations.

There are 2 easy ways to halt the script if the user has selected cancel and the result is null:

1. Call a function only if the result is not null.
2. If the conditional statement above occurs inside a function block, call return to exit the function.

Here’s a code sample for method 1:

var dom = fl.getDocumentDOM();
var xpanel = dom.xmlPanel(absoluteFileLocation);
if (result == null) {
//do nothing
} else {
run();
}

You’d then define a function that execute all of the requisite code:
function run(){
//all the action takes place here
}

If the result is null, the function is never triggered.

Here’s a sample for method 2:

run();
function run(){
var dom = fl.getDocumentDOM();
var xpanel = dom.xmlPanel(absoluteFileLocation);
if (result == null) return;
//continue executing otherwise
}

Essentially, the entire process is wrapped in a function, so it’s easy to jump right out when needed.

Either method will do, sometimes one method suits a particular script.

When you double-click an MXP (or ZXP) file, your operating system open your default version of Extension Manager. This may not be the version that you want, however. Suppose you have Flash Pro CS4 and Flash Pro CS5 installed. Your system will (probably) automatically launch Extension Manager CS5 when you attempt to install a new extension. This is okay if you want to install the extension in Flash CS5, but it will not be available in Flash CS4.

There are other issues that crop up when you have versions installed in multiple languages (and in some cases, if your language is not English). Luckily, there’s a simple way ensure that you’re using the correct version of Extension Manager.

1. Launch the version of Flash Pro (or Dreamweaver, or Fireworks) in which you’d like to install the extension.
2. Go to Help > Manage Extensions… and it will launch the matching installation of Extension Manager.

Once you’ve downloaded and installed the new version, you should see a button at the bottom of the SmartMouth panel that says Advanced…

New Advanced Features

The Advanced button will bring up a window with 2 new options.

Looping

Loop settings allow you to control the loop setting applied to the outputted symbol instance(s). This can be applied if you want to animate each mouth shape, rather than use static images.

Keyframe Frequency

Keyframe Frequency allows you to control the frequency of keyframes that are automatically generated (1s – every frame, 2s – every other frame, or 3s – every third frame). You can use this setting to animate your mouth at a frame rate lower than that of the rest of your animation. For example, your animation might be set to 30 fps, but you want your mouth to animate at 15 fps, so that the mouth doesn’t look frantic. In this case, you could select 2s.

The image below demonstrates the different outputs generated by altering the Keyframe Frequency.

These new features are based on user requests. Please let us know what you think!

Hope to see you there!

So, I wrote this script as a potential antidote to that problem. When the script is run (by opening with Flash Pro), it will allow you to either back-up or restore all of your configuration files for that installation of Flash Pro.

In certain specific cases (no guarantees)—where the machine, the username, and the Flash version remain consistent—this could be used to maintain a SmartMouth activation (as well as other extensions and settings) through a Flash, CS, or OS reinstall.

The script is pretty experimental at this point, so please use with caution.

Download
backup_restore_Flash_config.jsfl (right-click and choose Save Link As…)

Thanks to everyone for participating! We’ll have some more reviews and giveaways in the near future.

SWF Protector alters your SWF files so that it is more difficult to decompile them. This makes it more difficult for others to reverse engineer parts of your product that you’d like to remain secret. As has been noted on several other sites, there is no 100% sure method to protect your Flash content, but there are ways to make it more difficult. If someone is intent on breaking into your files, and they’re smart enough, they will find away. The usefulness in SWF encryption and obfuscation products is largely to reduce the number of people who can decompile your code by making decompilation more difficult.

That said, here are the criteria I used to review SWF Protector:

1. Usability: how easy is it to operate the application?
2. Is the SWF still fully-functional after protection? (You’d be surprised how many tools make the SWF inoperable).
3. Can the SWF be decompiled using readily available tools?
4. Bonus points for useful advanced features.

Testing

I tested the SWF produced from SWF Protector on 3 popular decompilers and had no luck reverse engineering the files. The protected SWF even crashed 1 of the decompilers. When I opened the SWF in the Flash Player, everything I set up still functioned properly. When testing SWF encryption tools in the past, I’ve found that the encryption breaks my SWF file. Not so with SWF Protector. It passed with flying colors on both criteria 2 and 3.

Features and Functionality

SWF Protector launches as a small, unassuming window.

You can press the only button available to locate the SWF you’d like to protect, or drag-and-drop the file onto SWF Protector (which I found handy).

You can then click Protect to generate a protected SWF (by default, the original is saved with _original appended to the file name).

Alternatively, you can toggle to Advanced Mode and choose to Obfuscate and/or Protect classes and code blocks within your SWF. You can choose to protect all classes within the SWF, or merely the ones that you’ve written. I’m not 100% sure what the difference between obfuscating and protecting is in this case.

Pros

• SWF Protector is available on Windows, Mac, and Linux.
• The interface is extremely easy to use (criteria 1) and the drag-and-drop functionality is handy.
• It keeps a back-up of your original SWF.
• Licenses are affordable ($4o – personal, $60 – business).

Cons

• SWF Protector doesn’t support the protection of SWC files.

Conclusion

In my testing, I’ve found that SWF Protector is an excellent solution if you want to quickly and easily add a reasonable amount of protection to your SWF files. It has a great price point for independent developers as well. The only downside is that if you want to also protect SWC files, you’ll have to go with another product.

Giveaway

As mentioned above, DComSoft has generously offered up 3 licenses of SWF Protector as a giveaway. The randomly chosen winners will be announced 1 week from today.

Ways to Enter

1. Tweet about this post. 1 point
2. Subscribe to our newletter. 2 points
3. Blog about this post. 2 points
4. Post a public link to this post on Google+ or Facebook. 1 point each
5. Post a comment on this entry.  1 point (Be sure to include your email address, it won’t be shown publicly, but we will use it to contact you if you win)

I recommend saving option 5 for last. When you post your comment, include links to your tweet and/or posts and mention if you subscribed to our newsletter. That way your entries will be easier for me to find.

Update (8/25/2011): The giveaway is now closed. I will be contacting (and announcing) the winners shortly.

Update #2 (8/25/2011): Winners have been announced.

Dave Logan has a wonderful command called Enter Graphic At Current Frame that resolves this issue. Many Flash animators use graphics symbols  so much that they would prefer “entering at the current frame” to be Flash’s default behavior when they double-click to edit a symbol. A number of these users have sent me requests through the Extension Request Form. So I put together this panel to essentially make “entering at the current frame” the default behavior. The panel simply has to be open for the behavior to work (the Auto jump box is checked by default). There are some extra buttons for some added fanciness.

This is a total freebie, but donations are appreciated (donate button located in the right-hand column).

Download
(Compatibility: Flash 8 & up)
FrameAim.mxp

Thanks to everyone who purchased SmartMouth and thanks to everyone who helped to spread the word!

We still encourage everyone to donate directly, voice your opinion to California governor, Jerry Brown, and if you live in California, please contact your representatives.

• Upped the Flash Player timeout limit from 15 to 45 seconds for files that take a long time to process.
• Added a warning for files that exceed Flash Professional’s 16,000 frame limit.
• Fixed an error that was occurring when serial numbers were entered incorrectly.
• Upped to the trial limits to 4 100-frame attempts per document.

These updates should help with issues encountered on larger files, as well as allow for more testing with the trial version. We still plan to release some new features to the extension in the near future.

Also, if you didn’t see the previous post, note that 50% of SmartMouth sales for the rest of this month will be donated to the California State Parks Foundation.