MiddleClickClose For Safari 3.1

As I reported two days ago, after I installed Safari 3.1, my MiddleClickClose extension stopped working. Well, I’ve gotten it working again. , but it doesn’t load under Safari < 3.0. So, only install this version if you are using Safari 3.1. If you are using an older Safari, use this one.

As before, I’m releasing this under the GPL.

My, What a Large Amount of Virtual Memory You Are Using

I just checked my Activity Monitor to see how much of my 6 gigabytes of RAM was in use. I was shocked (shocked!) to discover that a Java RMI server program (that I wrote) appeared to be using a bit more virtual memory than it should. Take a look at this screenshot of this process:

I’m sure it’s just a reporting error, but it was still funny to see.

Safari 3.1 Breaks My Middle Click Close Extension

If you install the new Safari 3.1, my MiddleClickClose extension stops working. The first time you launch Safari, SIMBL complains that the plugin hasn’t been tested with this version of Safari, but that’s easily fixed by putting the proper version 5525.13 in Info.plist for the tag MaxBundleVersion. Once that’s done, the extension loads, but doesn’t seem to do anything. The problem is that the system is no longer delivering a mouseUp event when you middle-click a tab. I’m not sure what’s going on, but I will look into it. I’ve become dependent on my middle-clicks…

Apple Tells Me “Thanks, But No Thanks”

Like 10 million other iPhone fanboys, I applied for the Apple iPhone developer program. Today, one week after applying, I received this email

Thank you for expressing interest in the iPhone Developer Program. We have received your enrollment request. As this time, the iPhone Developer Program is available to a limited number of developers and we plan to expand during the beta period. We will contact you again regarding your enrollment status at the appropriate time.

Thank you for applying.

Best regards,

iPhone Developer Program

And I’ve seen lots of other people on Twitter complaining of getting the same email. One disappointed reject said this

As I understand it, no one got in except for a handful of large partner companies alla Google.

It’s bad enough that the “free SDK” isn’t actually free since you have to pay $99 to be able to load your apps on your own iPhone, but now they’re rejecting hopeful developers in bulk. They ought to let everyone in who wants in. What’s the harm?

Gee… I wonder if I’m violating some NDA by blogging this? I’m sure some of the helpful souls on the xcode-users list will let me know if I am.

I Can Haz SSBB?

Oh, Yeah Oh yes, we haz it. Thomas has been playing for hours. I’ve played for an hour to two, myself. It’s very cool. We haven’t played online yet, but we’re working on it. Thomas and I have both created stages using the stage editor. I really like when you can customize a game.

iPhone SDK: No Joy For Me (So Far)

Like 10 bajillion other Mac fans yesterday, I downloaded the iPhone SDK. It took me four tries to get it, but I finally got it. I installed all 5.3 GB of it, and rebooted (reboot? what is this, Windows?) and then created a sample project, just like the ADC video shows. I excitedly clicked the ‘Build and Go’ button and… nothing. Well, not completely nothing, but not what was supposed to happen.

What was supposed to happen was that the app would build, the iPhone simulator would start up, the app would be loaded onto the simulator and then it would run. My app built, but the simulator didn’t run. All I saw was ‘Debugging of “Sample” ended normally’ in the Xcode status bar. I checked the Xcode console, and I get this every time I try to run the app:

[Session started at 2008-03-07 16:42:09 -0500.]
2008-03-07 16:42:10.772 Sample[1326:10b] Warning: CFFIXED_USER_HOME is not set!
2008-03-07 16:42:10.793 Sample[1326:10b] Warning: ASPEN_SIMULATOR_ROOT is not set!
Terminating since there is no system event server.
(Run the EventPump or pass the argument "-RegisterForSystemEvents" if you want to run without SpringBoard.

The Debugger has exited with status 0.

I’ve been exchanging emails with people inside Apple about this and the only suggestion so far was to run the uninstall script in /Developer/Library and reinstall. I have done both, but it still doesn’t work. Upon the suggestion of a friend, I created a new user account, logged in as that user and tried from there. Everything worked. Which means Xcode, the SDK and the simulator are all installed properly, but something in my account is dorking things up. I am loath to ditch my account and start over from scratch, but obviously something is wrong. Does anyone have any suggestions? I am awaiting another email from my guy at Apple, but if anyone else knows anything, please let me know. And when/if I get it working, I will document what worked here.

03/08/2008 21:47 Update: It’s working! w00t! It appears that if you are running Xcode in 64-bit mode, you get the errors that I got. If you run Xcode in 32-bit mode, it works. Now, I had switched to 64-bit mode when I installed Xcode 3.0, but when I installed 3.1, it got reset to 32-bit mode. Only it didn’t get reset, at least not for my user account. That’s why when I created another user account, it worked for him. I right-clicked on Xcode in my dock and selected ‘Show in Finder.’ Then I right-clicked on the Xcode icon and selected ‘Get Info.’ On the Get Info screen is a checkbox labeled ‘Open in 32 Bit Mode’ and it was checked. I unchecked it, launched Xcode and the same problem happened. Then I re-checked it, re-launched Xcode, and now the simulator works. If I uncheck it, the problem returns, proving the cause. Thus, you must run Xcode in 32-bit mode and even if you think you’re running in 32-bit mode, it wouldn’t hurt to toggle that checkbox a time or two just to make sure. (Thanks to Daniel Cliche who suggested the 64-bit problem.)