Right Click Desktop > Graphics Properties … > Options and Support > Hot Key Manager > Uncheck the box for Hot Key Functionality

 

Settings > Editor > Highlight usages of element at caret

• Right click your project > Module Settings
• Click the Dependencies tab in the window that opens
• Double click your Java JDK version (ie 1.6)
• Click the Documentation Paths tab
• Click Specify URL…
• Enter the java docs url (which is currently http://download.oracle.com/javase/6/docs/api/) and click Ok

That should give you access to the full docs when you click Ctrl + Q. Another neat trick I’ve learned is that clicking Shift+F1 opens a browser and directly brings up the JavaDocs page.

trace(new Error().getStackTrace());

haloBlue = #009DFF
haloGreen = #80FF4D
haloOrange = #FFB600
haloSilver = #AECAD9


<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">

<mx:Script>
<![CDATA[
import mx.controls.Label;

private function getHex(evt:Event):void {
var lbl:Label = evt.currentTarget as Label;
lbl.text += "#" + ("000000" + lbl.getStyle("color").toString(16)).substr(-6).toUpperCase();
}
]]>
</mx:Script>

<mx:Label id="haloBlueLabel"
text="haloBlue = "
color="haloBlue"
initialize="getHex(event);" />

</mx:Application>


skin: ClassReference("mx.skins.ProgrammaticSkin");


override public function set verticalScrollBar(value:ScrollBar):void
{
super.verticalScrollBar = value;

if (value == null) {
// the scroll-bar is being removed, reset width to original values
this.width = defaultWidth;
} else {
// scroll bar is being enabled, adjust width to include it
this.width = defaultWidth + ScrollBar.THICKNESS;
}
}


There are two options for preloading a SWF that dynamically loads movie clips that are exported in the first frame.  To learn more about this issue, see here (www.senocular.com/flash/tutorials/preloading/#loadingcomplications).  The first is to create a ‘loading’ frame inserted after the end of your preloading frames where you can manually load each movie.  So instead of setting each movie to export, add all the movies to this single frame instead.  This will allow the preloader animation itself to load and start running before any movie clips (which will later be dynamically called) are loaded.  When movie clips are dynamically called, by default, Flash loads them in the very first frame so that they are available any any point in the time line.  While this solution would work, it seems to add extra work and remove the flexibility of dynamically adding movie clips in the first place.  Since it had been over a year since I last update my site, I had no interest in going back through it to find and change every movie clip I exported to the first frame to instead load in a single frame after my preloading animation.

Fortunately, I came stumbled across another (and in my opinion better) option, loading my SWF from another SWF to eliminate the issue of first frame exporting completely.  To implement this scenario I created a new Flash SWF containing my preloading animation, which after execution, loaded my original SWF into it.  This way I could ensure that the preloading animation began before the orginal movie clips even had a chance to.  To read more about this, see this link (www.senocular.com/flash/tutorials/preloading/#loadingexternalcontent).

The final solution I ended up using on my site was largely based off of the MovieClipLoader class and Example 5 which can be found here (http://www.senocular.com/flash/tutorials/preloading/#themoviecliploaderclass).  So just like that, LindsayRyerse.com finally comes complete with a loading bar which will hopefully ease any user frustration.