Why was my OS X mouse behaving so badly?

It had been bugging me for a while, but now I was going over the edge.

OS X 10.4.11 wasn't responding to my mouse clicks. I was double, triple and quadruple clicking where one should have done.

What had gone wrong? Some recent update? Something stealing the mouse clicks?

I keep my system very plain, so I decided to check into a new mouse driver. It had been a while since I'd updated my Microsoft IntelliPoint driver -- years, come to think of it.

I installed the new IntelliPoint and IntelliType Pro driver from Apple's site. The reboot took a long time, the mouse install seemed to require some major rebuilding.

The new driver had loads of new options, but my mouse clicks were still being missed. Now, however, the driver told me my battery was low.

New batteries, but the problem remained. The driver had one more diagnostic though ... my signal was oddly weak.

Yes! The small wireless receiver (this is pre-Bluetooth) had fallen off my desk, and was now buried between the back wall and the back of the desk. Restoring the receiver restored the signal -- and my mouse clicks.

Of course the real problem was that I'd lost my receiver, but it was odd that I didn't get the battery and signal warnings until I installed the new driver. My IntelliMouse driver was ancient, probably inherited from a 10.3 build. I wonder if some recent update didn't knock out the battery warnings it used to give; Apple can't possibly test against ancient drivers.

Really, these computer systems are a wee bit complex.

I do like the new mouse options however, especially Microsoft's acceleration support. I feel as though I got a new mouse out of the deal.

Google Docs: still no working clipboard

I've been using Google Docs for ages, and there's been no progress in providing any kind of reasonable clipboard functionality with any OS X browser. We're told to use ctrl-c to work with the system clipboard instead of using the native Google Docs clipboard. Of course that shortcut works for Firefox on OS X, but not Safari.

Honestly, Google Apps is still a semi-useful toy compared to a desktop application. Progress is very slow.

Firefox noscript add-on - time to start using it

A recent large scale hack of Microsoft's IIS web server means that lots of reputable web sites may be hosting exploits more commonly seen on the shady side of the net.

So it's probably time to start using the Firefox NoScript add-on ...

Hundreds of Thousands of Microsoft Web Servers Hacked - Security Fix

There is a great add-on for Firefox called "noscript," which blocks these kinds of Javascript exploits from running automatically if a user happens to visit a hacked site. Currently, there is no such protection for IE users, and disallowing Javascript entirely isn't really an option on today's World Wide Web. True, you can fiddle with multiple settings in IE to add certain sites to your "Trusted Zone," but that option has never struck me as very practical or scalable.

I've been using it for a few days. I whitelisted a number of the Google sites I use (if they're hacked we're all doomed) and so far it's been easy to enable JavaScript when needed by clicking on the S icon.

Video editing - lord, this is ugly

I'm pretty disgusted with iMovie '08, so I decided to read a review of Final Cut Express 4.

Yuck.

MacWorld desperately tries to say nice things about Apple, but despite the "4 mouse" rating the review reveals a right mess. Different behaviors on different processors, inability to import some formats iMovie '08 handles, etc, etc.

Video editing was always pretty complex, but I think the profusion of codecs and file formats has driven it over the cliff.

Apple's offerings are pretty sad at the moment (iMovie HD was the closest they got to a good solution, and they abandoned it). Unfortunately I think Apple is the only consumer video option for the Mac.

Digital-TV converters: choices for the Saint Paul area

A local paper's tech blog reviews Digital-TV converters available locally. His preference is the "Digital Stream DTX9900 sold by RadioShack". I need to spend my vouchers before they expire, so I'll probably follow his lead here.

From what I've read elsewhere broadcast digital may require a fairly expensive antenna investment. So the converters are only a part of the cost. We have very cheap antennae; I'll report on what we find in our real world testing. All we need is for one sports channel to come in so my son can spend his tv-time credits.

Update 5/4/08: Bloody 'ell, it worked.

QuickTime Player: saving the configuration files

QuickTime Player Pro AppleScript driven batch translation from FLIP Video 3ivx to Apple Intermediate codec requires a QuickTime configuration (.set) file.

You can't save a configuration file from QuickTime Player Pro. (How hard would that have been?)

You need to open video file, set up the export settings, then run an AppleScript like this one:

tell application "QuickTime Player"
tell first document
save export settings for QuickTime movie to file "BootDrive:Users:jfaughnan:Documents:aic2.set"
end tell
end tell

You'll need to edit the "BootDrive ..." stuff to match your hard drive (Volume) name and user name.

What a nuisance!

Apple stripped AppleScript functionality from QuickTime Player - in a fairly rude way

Once upon a time you could use AppleScript to make QuickTime Player do many of the tricks that QuickTime Player Pro is supposed to do. In those days people wrote scripts to do things like batch file translation:

Gordon's Tech: FLIP Video Ultra camcorder: iMovie HD works, iMovie '08 doesn't

Update 3/30/2008: I found an AppleScript that should do what I need. It tells QuickTime Player to open multiple AVI files, process them to DV stream, then delete the originals. Unfortunately, it's giving me cryptic error messages.

Update 3/31/2008: I'm beginning to think Apple quietly disabled AppleScript driven conversion in QT Player. Nobody seems to know anything about it.

As you can probably guess my theory of 3/31 seems to be correct.

When I ran those scripts with QuickTime Player, they simply didn't work. No error messages, but the AppleScript APIs didn't seem to do anything.

I paid for QuickTime Player Pro and now the original scripts work.

This seems kind of obnoxious. At the very least QuickTime Player should have produced an error message like "AppleScript functionality requires QuickTime Player Pro". Apple wasted a fair bit of my time.