Archive › September, 2009

Fonts not antialiased correctly in Snow Leopard?

In my ongoing saga that is upgrading to Snow Leopard (mainly so I could search in specific folders from the finder), I just fixed yet another issue: The fonts on my 26″ LG screen looked awful, particularly in Eclipse. Sure enough, there is a bug that causes Apple not to detect that my screen is capable of doing sub-pixel anti-aliasing. Luckily I found a fix on jjgod’s blog.

Run this command from your terminal, then log out and log in:

[code lang="as3"]defaults -currentHost write -globalDomain AppleFontSmoothing -int 2[/code]

Woo hoo! Text looks good again.

If people had this many problems with a Windows Upgrade, they would have been crucified everywhere. Apple botches an upgrade and it’s radio silence…

And did I mention the color profile issue? Oh yeah, after you upgrade to Snow Leopard, your screen might look washed out because they forgot to include a the right color profile for your LCD. Or, as in my case, it just looks weird and I wasn’t sure why. All I knew is that I had to recalibrate it. Even after calibrating, it still didn’t look quite right to me, so I ended up picking one of the other included color profiles and going with that.

You can read more about it here, here, here, and here.

Comments ( 0 )

More Ant/Adobe AIR/Snow Leopard fun

For some reason, after I upgraded to Snow Leopard, our builds of YNAB 3 weren’t running correctly. They worked fine from the debugger, but the builds spit out by our build machine (powered by Hudson, which rocks) weren’t functioning. Turns out that it was because my ANT script that FX2Ant was spitting out had a line like this:

[code lang="as3"]<arg value="-runtime-shared-library-path+=${PROJECT_FRAMEWORKS}/libs/framework.swc,framework_3.3.0.4852.swz,,framework_3.3.0.4852.swf,"/>[/code]

In short, my understanding is that it was attempting to dynamically load my Flex libraries. After I upgraded to Snow Leopard, I no longer had these Flex libraries cached on my machine, so it crashed on startup. Of course, since Flex/AIR/Flash has no #$@!#$ way to tell the user about an uncaught runtime error, I had to use adl to debug my air package to get to the bottom of it.

I added this line to the ant script:

<arg value=”-static-link-runtime-shared-libraries”/>

(which Flex Builder already does) and all was well again.

Comments ( 0 )

Starting Firefox in Safe Mode on Snow Leopard (Mac OS X 10.6)

According to, this is the way you start Firefox in safe mode on the Mac:

go to Utilities (in the Applications folder) and open Terminal, then run (for Firefox):
/Applications/ -safe-mode

But when I did that, I got a lot of errors:

[code lang="as3"]dyld: Library not loaded: /usr/lib/libsqlite3.dylib
Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security
Reason: Incompatible library version: Security requires version 9.0.0 or later, but libsqlite3.dylib provides version 1.0.0
/Applications/ line 131: 457 Trace/BPT trap "$prog" ${1+"$@"}
[code lang="as3"]

But add a "-bin" to the end of the firefox command, and all is well:

[code lang="as3"]/Applications/ -safe-mode[/code]

Now I still have to figure out why Firefox won't let me click on any Windows when it starts. I think it might have to do with the new 1Password beta I just installed, but I'll know more soon.

UPDATE (9/14/09): Nope! It wasn't 1Password! (Man, I love that software.) I disabled all of my plugins and then re-enabled them one at a time, and it seems to work well now. Just another Snow Leopard fluke...

Comments ( 0 )

Building an AIR file from the command line is MUCH harder than it should be

I need to take some time to write about my saga in getting a continuous integration system set up with our Adobe AIR product (YNAB 3), but for now let me just say: Using ANT to build an AIR project is a lot more finicky than it needs to be. Why, oh why can’t I just tell Flex Builder to build my projects in headless mode? Luckily, it looks like that’s exactly what Flex 4 will offer, but until then, it’s a major pain to keep our Flex Builder projects in sync with our Ant scripts. I’ll write more later…

Comments ( 0 )

Photoshop “Not Responding”?

Yeah, I just had that happen, and here’s what I did to fix it. It was completely frozen after a couple of hours of work. Yeah, I should have been saving, but I didn’t…Anyway, what finally worked was telling Windows to restart. Lots of programs started shutting down, and then it told me Photoshop wasn’t responding…Instead of hitting “End Now”, I hit the “X” on that window and by that time Photoshop was already responsive again! Woo hoo!

I think it had to do with a ZumoDrive error to be honest, because it got responsive shortly after ZumoDrive shut down…And I’ve had Photoshop crash on me before when saving to ZumoDrive. Anyone else ever noticed ZumoDrive strangeness when working with Photoshop?

Comments ( 0 )