This will be the start of a new series of blog posts for me focused around my flexdateutils library that I’ve published to Google code at http://code.google.com/p/flexdateutils/
I first began writing this code in response to some of what I felt were shortcomings to the Flex framework in handling date manipulation. It seemed that just about every other programming language had its own library of date functions, but the few that Flex had made it very difficult to do anything to a date unless you managed it yourself. And so was born FlexDateUtils.
Each day I will try to post at least one method from the library and explain the code a little. If it’s a very basic method, I’ll probably add a couple more methods. Most of the methods were created from ColdFusion’s date library as those have been very useful to me whenever I have had any kind of date manipulation. I have very rarely had to add any of my own code to get back what I needed from ColdFusion’s date functions.
I am hoping this will be a useful group of functions to other developers, and, who knows, perhaps Adobe will even think that it is something that should be added to their standard Flex framework 
Last week I ran into an issue (or so I thought) with my debugger. I was trying to debug some code on my local machine, but for some reason, the debugger in Flex Builder could not seem to find the SWF that was being built. I would click debug, a new window would open, but nothing happened in my Flex Builder to indicate that it had reached a breakpoint. After playing around with it for a little while, I decided to close out of Flex Builder and reopen it, in hopes that *something* would happen that would indicate why nothing was happening. After restart, and trying to run the debug again, Flex Builder decided to actually let me know what was happening.
In my work environment, my exported release builds and my debug builds are both built to the same spot, which is due to our upgrade process to Flex being an incremental process (from our current HTML + CFM app). In order to add some values to the Flex app, I write them to the HTML page, thus I decided to build them to the same spot. I had not realized at the time that I had exported a release build right before lunch, then when I returned, I was trying to debug the release build. Due to the very nature of the release build, the debug is removed, thus Flex Builder was not able to stop at the breakpoints. For some reason, Flex Builder wasn’t telling me this initially though (even after I had cleaned the project).
My steps to fixing most Flex weirdness (i.e. something isn’t happening that I feel should be happening), is to clean a project first, then restart Flex Builder, if neither of those work, restarting my PC is next. One of those will usually fix the problem .
Don’t know how many people this affects, but it’s been annoying me for a while.
When using CFEclipse in Flex Builder/viewing ColdFusion files, line numbers do not show up in the gutter, no matter how many times (or places) that you select “Show Line Numbers”.
In order to fix this, close out of Flex Builder or Eclipse and go to wherever you have Flex Builder preferences installed (which for me was in my “My Documents” on my C: drive), not the main Program Files directory.
This was where mine was located C:\Documents and Settings\(my logged in account)\My Documents\Flex Builder 3\.metadata\.plugins\org.eclipse.core.runtime\.settings
Once you are in this directory, back up then open up
org.cfeclipse.cfml.prefs
Once inside this, add the line
lineNumberRuler=true
and save the file
Now you can open Flex Builder/Eclipse again, and line numbers should be showing up for you when view ColdFusion files.
Just want to thank Francois Levesque over at http://blog.critical-web.com/blog for this. This has saved me many headaches.