Example 1

trace(getIncrementFilePath("gallery/image01.png")); //returns gallery/image02.png

Example 2
Creating incremented filepaths in a loop.

var path:String="gallery/image01.png";

var i:int=0;
while (i < 10)
{
	path=getIncrementFilePath(path);
	trace(path);
	i++;
}

/*
trace output
===================
gallery/image02.png
gallery/image03.png
gallery/image04.png
gallery/image05.png
gallery/image06.png
gallery/image07.png
gallery/image08.png
gallery/image09.png
gallery/image10.png
gallery/image11.png
*/

The source

/**
 * Gets a new filepath with incremented digits .
 *
 * @param filepath The filepath to get an incremented filepath from.
 * @param incrementPrefix If true, any digit prefixes will be incremented in the filepath. This is false by default.
 * @param incrementSuffix If true, any digit suffixes will be incremented in the filepath. This is true by default.
 * @return A filepath with the filename's digit suffix or prefix incremented.
 * Returns an empty String if there are no numbers to increment.
 **/
function getIncrementFilePath(filepath:String="",incrementPrefix:Boolean=false,incrementSuffix:Boolean=true):String
{
	var s:String="";
	var bre:RegExp=/^\d+/mig;
	var ere:RegExp=/\d+$/mig;
	var dpath:String=(filepath.match(/^.+\//mig)[0])||"";
	var fs:String=filepath.replace(/^.+(\/|\\)/mig,"");
	var ext:String=fs.replace(/^.+\./mig,"");
	var fn:String=fs.replace(/\.\w+$/mig,"");
	var bd:String=(fn.match(bre))[0]||"";
	var ed:String=(fn.match(ere))[0]||"";
	var mids:String=fn.replace(bre,"").replace(ere,"");
	var md:String=mids.replace(/^[^\d]+|[^\d]+$/mig,"");
	var dlen:int;
	var tempstr:String="";
	var tempn:int;
	var n:int=0;
	if (incrementPrefix)
	{
		if (bd == "")
		{
			return "";
		}
		dlen=String((bd.match(/^0+/mig)[0])||"").length;
		tempn=parseInt(bd)+1;
		while (n < dlen)
		{
			tempstr+="0";
			n++;
		}
		if (String(tempstr+tempn).length > bd.length)
		{
			tempstr=tempstr.substr(1,tempstr.length);
		}
		bd=tempstr+tempn;
	}
	if (incrementSuffix)
	{
		if (ed == "")
		{
			return "";
		}
		dlen=String((ed.match(/^0+/mig)[0])||"").length;
		tempn=parseInt(ed)+1;
		while (n < dlen)
		{
			tempstr+="0";
			n++;
		}
		if (String(tempstr+tempn).length > ed.length)
		{
			tempstr=tempstr.substr(1,tempstr.length);
		}
		ed=tempstr+tempn;
	}
	if (ext != "")
	{
		ext="."+ext;
	}
	s=dpath+bd+mids+ed+ext;
	return s;
}

The "toXMLString()" method does this automatically on attributes.
Attributes are typed as XMLList.

 
var myXmlList:XMLList=XMLList(<B><P name="Orange"/><P name="Grape"/><P name="Pear"/></B>).P;
trace(myXmlList..@name.toXMLString());
//Outputs multiple values of all "name" attributes separated with carriage returns automatically.
Orange
Grape
Pear
 

Putting the values of an XMLList as an Array might be useful also.

Being separated by carriage returns makes it easy to convert to an Array by using the String "split" method.

Wrap this into a function for easy use.

 
function xmllistToArray(list:XMLList):Array
             {
                 return list.toXMLString().split("\n");
             }
 

Dana Barrett: Are you the Keymaster?
Dr. Peter Venkman: Yes. Actually I'm a friend of his, he asked me to meet him here.
-Ghostbusters

It's been a whole year since I needed to use the KeyManager class and from comments I've been made aware of bugs in my script.
I was hoping the scripts would be a sufficient start that should issues arrive, others would come up with work-a-rounds. (Thank you to all who noted solutions and problems.)

Lately I was needing to write some keyboard interactivity again and I wanted to add some features to help simplify newer task...also fix a couple of things in the process.
In Flex, a lot of coding deals with listening to events. The KeyManager needed events for the tasks I was working on. Callback functions where ok at first but adding "KEY_DOWN", "KEY_UP" and "KEY_SEQUENCE" events help make the class more useful for monitoring status. Monitoring events give more options for handling keyboard activity in one handler function versus using a separate function for each keyboard combination. So now I've updated the class to have both.

This is a simple example of using the KeyManager class with the added features and KeyManagerEvent.
The example application displays the key activity as you press assigned keys. The functions executed should give a simple idea of how you could expand and add your own application/game logic.

The KeyManager is written for Flex and AS3 only projects.
I decided to share this class since it solves my current task, but I know it is not a solution for everything. Feel free to comment on it's issues or what's needed.
View Source

In Flash Builder 4

 
 
                        public static function isDevEnvironment():Boolean
			{
				return mx.core.FlexGlobals.topLevelApplication.url.search(/^file|^\w:\\ig/) != -1;
			}
 

In Flex Builder 3

 
			public static function isDevEnvironment():Boolean
			{
				return mx.core.Application.application.url.search(/^file|^\w:\\ig/) != -1;
			}
 

Here I extended the TitleWindow to make it be automatically added with the PopUpManager.
Also all the child components get carried over after PopUpManager is used.
I did this so I could lazily use MXML and all references to this component instance stay intact, because the PopUpManager is using the same instance of the MXML component.

The "Move Left" and "Move Right" buttons show that the references are ok.

MXML in "net/keithhair/FloatWindow.mxml"

 
<?xml version="1.0" encoding="utf-8"?>
<s:TitleWindow creationComplete="init()"
			   xmlns:fx="http://ns.adobe.com/mxml/2009"
			   xmlns:s="library://ns.adobe.com/flex/spark"
			   xmlns:mx="library://ns.adobe.com/flex/mx"
			   autoLayout="true"
			   width="400"
			   height="300">
	<fx:Script>
		<![CDATA[
			import mx.events.CloseEvent;
			import mx.managers.PopUpManager;
			import spark.components.Group;
			import spark.components.VGroup;
 
			protected var _vgroup:Group;
 
			protected function init():void
			{
				var p:String;
				var n:int;
				var a:Array=[];
				var _parent:DisplayObject=parent;
				//---------------------------------------------
				//Remove all the child elements store
				//the references in an Array
				//---------------------------------------------
				n=numElements - 1;
				while (n > -1)
				{
					a.push(removeElementAt(n));
					n--;
				}
				Group(parent).removeElement(this);
				//---------------------------------------------
				//Add a popup of a this TitleWindow instance,
				//Create a layout container and add all
				//the children back into it.
				//---------------------------------------------
				PopUpManager.addPopUp(this, _parent);
				n=a.length - 1;
				_vgroup=new VGroup();
				_vgroup.setStyle("top",5);
				_vgroup.setStyle("bottom",5);
				_vgroup.setStyle("left",5);
				_vgroup.setStyle("right",5);
				addElement(_vgroup);
				while (n > -1)
				{
					_vgroup.addElement(a[n]);
					n--;
				}
				addEventListener(CloseEvent.CLOSE, closer);
				PopUpManager.centerPopUp(this);
				p=null;
				n=0;
				a=null;
			}
 
			protected function closer(evt:CloseEvent):void
			{
                                removeEventListener(CloseEvent.CLOSE, arguments.callee);
				PopUpManager.removePopUp(this);
			}
		]]>
	</fx:Script>
</s:TitleWindow>
 

Now I can simply use MXML to make my draggable windows.
The window is draggable and all the
MXML children are there too.

 
	<keithhair:FloatWindow id="mywindow"
			       title="My Window"
			       width="250"
			       height="300">
		<mx:TabNavigator width="100%"
				 height="100%">
			<mx:VBox label="Buttons">
				<s:Button/>
				<s:Button/>
				<s:Button/>
			</mx:VBox>
			<mx:VBox label="Checkboxes">
				<s:CheckBox/>
				<s:CheckBox/>
				<s:CheckBox/>
			</mx:VBox>
			<mx:VBox label="TextAreas">
				<s:TextArea/>
				<s:TextArea/>
			</mx:VBox>
		</mx:TabNavigator>
	</keithhair:FloatWindow>
 

If you know of a more efficient way that does this or can make this better just add your comments to my blog.

I love automating redundant tasks. One thing that bugs me when importing graphical assets to Flash's stage is having to resize the document to what I imported. I like that I can do this by going to the Document Properties and setting the document to match the content size, but if I have to do this each time I import/export content it becomes a irksome chore. I write JSFL scripts that run tasks on multiple files, having a "match contents" function would be useful to me in my case...maybe to you as well. I do not see a JSFL way to do this. (Maybe there is and I had a brain fart?). Until then, here is a script I wrote to do it in JSFL...

/*****************************************************************************************
What:	Document_to_Content_Size.jsfl
		JSFL Command for Flash (8+) that will resize the document to fit the content
		that is on the stage in the authoring environment.

Why:		Yep, this action can also be done by going to the Document Properties
		and setting "match" to "contents". However, I have not
		found a way to do this same action within JSFL script
		If you know a JSFL way to do this same action easier contact me.		

Date:		March 21, 2010
Author:	Keith Hair
Contact	khos2007@gmail.com
Web:		keith-hair.net		

INSTALL:
		If you deal with JSFL you probably know what to do, but anyway...
		Save this script with a ".jsfl" extension and put in:
		"Your Flash installation folder\en\First Run\Commands" folder
		Or just put it anywhere and double-click the file.

LEGAL STUFF:
		This script is free for whatever, just improve it or say hello! 		

NOTE:
		This is primarily for resizing the Flash
		document to fit content that is imported to the stage.
		Resizing is buggy with Component instances.

******************************************************************************************/
fl.outputPanel.clear();
runApp();
function runApp()
{
	var doc=fl.getDocumentDOM();
	var element;
	var docw=1;
	var doch=1;
	var fn=0;
	var ln=0;
	var en=0;
	var tframes;
	var layer;
	var frame;
	var ox;
	var oy;
	var left=null;
	var right=null;
	var top=null;
	var bottom=null;
	var cf=doc.getTimeline().currentFrame;
	while(ln < doc.getTimeline().layerCount)
	{
		layer=doc.getTimeline().layers[ln];
		tframes=layer.frameCount;
		fn=0;
		while(fn < tframes)
		{
			doc.getTimeline().currentFrame = fn;
			frame=layer.frames[fn];
			en=0;
			while(en < frame.elements.length)
			{
				element = frame.elements[en];
				ox=element.x;
				oy=element.y;
				if(left == null){
					left=ox;
				}
				if(right == null){
					right=ox+element.width;
				}
				if(top == null){
					top=oy;
				}
				if(bottom == null){
					bottom=oy+element.height;
				}

				left=Math.min(ox,left);
				right=Math.max(ox+element.width,right);
				top=Math.min(oy,top);
				bottom=Math.max(oy+element.height,bottom);
				en++;
			}
			fn++;
		}
		ln++;
	}
	fl.trace("CURRENT SIZE-->\t"+doc.width+" x "+doc.height);
	docw=Math.round(right-left);
	doch=Math.round(bottom-top);
	moveAllElementsBy(-left,-top);
	doc.width=docw;
	doc.height=doch;
	fl.trace("NEW SIZE-->\t\t\t"+doc.width+" x "+doc.height);
	doc.getTimeline().currentFrame=cf;
}

function moveAllElementsBy(tx,ty)
{
	doc=fl.getDocumentDOM();
	var element;
	var fn=0;
	var ln=0;
	var en=0;
	var tframes;
	var layer;
	var frame;
	var otp;
	while(ln < doc.getTimeline().layerCount)
	{
		layer=doc.getTimeline().layers[ln];
		tframes=layer.frameCount;
		fn=0;
		while(fn < tframes)
		{
			doc.getTimeline().currentFrame = fn;
			frame=layer.frames[fn];
			en=0;
			while(en < frame.elements.length)
			{
				element=frame.elements[en];
				element.x+=tx;
				element.y+=ty;
				if(element.elementType.search(/instance|text/mig) == -1){
					element.x+=element.width/2;
					element.y+=element.height/2;
				}

				en++;
			}
			fn++;
		}
		ln++;
	}

}

When an app or game is written we "expect" the user to precisely press the proper key or key combination at a time to execute programmatic actions. However, most of us have ten fingers and we use more than one finger to press more than one button on the keyboard. The expected program reaction from multiple fingered keyboard input might not occur because you have another function executing when you expect just one at a time.

Key Combinations
Imagine you are using the keyboard to play a game. The RIGHT arrow key is for moving your character right, the LEFT arrow key is for moving your character LEFT.
Ok, the action in this game is heating up, you are pressing LEFT to avoid the lasers shooting at you. You successfully dodged the lasers, now you press RIGHT to move in and attack...but in the heat of battle, your other finger is still on the LEFT button. What happens now is your character most likely gets stuck, because both movement keys are pressed telling the character to go in opposite directions!

In some cases allowing multiple key presses is how you want the app to react. For example you want the user to press both UP and RIGHT keys to move the characters in a diagonal direction. When to allow this and when not can be different among all of the control buttons. It becomes messy having to write "If" and "switch" statements to make the KeyboardEvent listeners work according to the different controls needed.

Key Sequences
If you love video games cheats or the easter eggs developers sometimes place in apps you'll remember to access them, you will usually enter in a sequence of key presses. If you entered the sequence successfully you would have access to cool game cheats or some special developer mode of an application.

KeyManager
For the above reasons I've written a KeyManager class to add key control that allows individual keys/keycombos the option to cancel out the any previous key/keycombo that are pressed down...and when key/keycombos are released, whatever key/keycombo that are still pressed will be active again. And for detecting key press sequences the KeyManager class will allow also.

This is a basic example using KeyManager. The "addKey" method is for adding key press combos and the "addKeySequence" is for obviously adding
key press sequences.

In the working flash example, you can click "singular combos" checkbox to false, to see the problem described previously about the character getting stuck when pressing RIGHT and LEFT key at the same time. When you set the checkbox back to true you will notice how each new key press overrides any others that are still down. This results in responsive execution if a user has a habit of holding down other keys while pressing new ones..

Also in the working sample above if you enter in the proper key sequence you will be rewarded with an "Easter Egg" to view the source and FLA.

Example usage:

import net.keithhair.KeyManager;

var keyManager:KeyManager;
keyManager=new KeyManager(stage);
keyManager.addKey(["right"], goRight,stopRight,"control1");
keyManager.addKey(["left"], goLeft,stopLeft,"control2");
keyManager.addKey(["up"], goUp,stopUp,"control3");
keyManager.addKey(["down"], goDown,stopDown,"control4");
keyManager.addKey(["shift","w","t"], toggleWindow);
keyManager.addKeySequence(["up","up","down","down","left","right","left","right"],openEasterEgg);

I've seen lots of really great knobs, dials, and gauge components. The intended way a person would build their app to use one would most likely be varied . That makes each of these kinds of controls  special because its difficult to make a control that fits a very broad range of functionality/look-n-feel, and probably why I have yet to see "one knob to rule them all".   Sliders, and Buttons are pretty straight forward, but not the "Knob" type of control.

Knobs can be just like a glass of tea. Some like a twist of lemon in it, or twist of lime etc. Just like others who have made their own controls tailor made to their needs, I have done with my knob.  The good thing about that is there's always more than one person who share the same preference on how a knob should function.  I've made many custom knobs that were built for small and simple duties. I'd like to make a knob to share here that is more reusable and cover wider ranges of functionality than the older ones I've built.  The knob displayed here is configurable but not skinnable, I've chosen to draw my knob dynamically with ActionScript's drawing API.  I hope to release this one after fixing some problems in my spare time.

View demo