I just installed Subclipse 1.6 in my Flex Builder as there was some conflict between it and my TortoiseSVN install. I like to do my commits and updates via Eclipse so I’m not switching out to my Explorer window for quick commits. If there is any conflict resolution needed, or I need a little more fine grained control, I switch out to Tortoise (as Subclipse doesn’t do as good a job currently).
After I upgraded from Subclipse 1.4 to 1.6, for some reason (I pretty sure it was Subclipse as I didn’t upgrade anything else), it decided that it didn’t like my comment color in CFEclipse or my highlight color and decided to randomly alter those colors to something else…a really weird, dark green for the comment background color and a much darker shade of blue for the text highlight color. To my mild case of OCD, that is just unacceptable 
Plus it’s just really difficult to read *any* text with a dark green background
If you want to switch these options back to their original colors, do the following:
Window -> Preferences -> CFEclipse -> Editor -> CFML Colours -> CFML Comment Background
I switched this one back to white from dark green.
and
Window -> Preferences -> CFEclipse -> Editor -> Appearance color options -> Selection background color
This one I had to create a new custom color and set it to Red 49, Green 106, and Blue 197 (this, I think, is the windows highlight color).
So far these are the only things I’ve found that it changes. I’ll post new updates if I find anything else.
Ha ha! I figured out (after just blogging my frustration in my previous post) how to change the Additional compiler arguments that automatically are added when creating a new project from ja_JP to en_US.
There is a file called config.xml (on my PC it is located in C:\Program Files\Adobe\Flex Builder 3 Plug-in\eclipse\plugins\com.adobe.flexbuilder.flex_3.0.214193) that gets installed when updating via the Adobe updater. I’m not quite sure what happened, but it decided that my compiler arguments should be set to ja_JP. In order to fix this problem, just change this line from
to
This will now add en_US as an additional compiler argument instead of ja_JP. Now I can get back to coding again
This is annoying the heck out of me. For some reason, I’m not sure when, my locale got set to ja_JP instead of en_US I did the update in eclipse and I’m wondering if it somehow got the japanese version of the SDK instead of the US version.
Each time I create a new project I get -locale ja_JP added to the compiler arguments. It’s an easy fix, just remove that or change it to en_US, but I have to do that each time I create a new project. If I could even find the file that’s making that setting, I would be happy to manually alter it, but I haven’t even been able to find that. My flex-config.xml file appears to be set to en_US also, so I have no clue how ja_JP is getting in there.
If anyone has any ideas, I’d be extremely grateful.
I had decided to create a demo application for my Flex Date Utils library. I thought it might be nice for people to just be able to see exactly what the library can do without having to download it and compile it. Right now it is just for the DateUtils portion of the library, but I’ll be adding Holiday and BusinessDay to the mix soon.
In order to make what I did more visible, I decided to enable the source code view when exporting the release build of the project. After exporting the file and FTP’ing it to the server, I started to have some difficulties getting the source code view working properly. Rather than wasting more time trying to get it working, I decided to just uncheck the Enable View Source check box, and re-export the project. However, when I went to my swf and right clicked on it, “View Source” was still an option in the Context Menu. I went back and tried cleaning my project, re-exporting it, deleting the swf and recreating the project. Nothing seemed to be working.
I then figured I would try creating a new project and placing it under there. As I was pasting the new application file, I noticed one new line had been added to my file
viewSourceURL=”srcview/index.html”
Apparently when the compiler enabled “View Source”, it adds this line of code. However, when it re-compiles the code with “View Source” disabled, it does not remove that attribute from the application tag. 30 minutes and lots of yelling later, this has now fixed the problem. It would be nice if Adobe included this little tidbit in their livedocs as “make sure to check this”.
The demo app can be viewed here for anyone interested.
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.