Cleaning an Apple Mighty Mouse Scroll Ball

I’ve recently started using my Macbook Pro a bit more to do some web development stuff, and I quickly ran into an ongoing problem. In a rare case of design failure, the scroll ball on the Mighty Mouse just doesn’t work after extended use. The most common cause of this is a buildup of dirt and gunk around the scroll ball and its surrounding sensors. After some google searching, I found a few different methods for cleaning from the hardcore to the basic (push down and rub). In the end I went with a slightly modified version of this kid’s method which has thus far worked a treat.
Continue reading

Sharing GLUT Code Between Windows and Mac OS X

If you’ve seen my last post, you’re aware that I’ve been playing with OpenGL and GLUT for a uni subject. As I like to straddle the OS fence and use a mixture of Windows Vista x64, Windows XP and Mac OS X 10.5, I like to have platform independent solutions to problems. The latest little issue I’ve come across regarding GLUT apps is that GLUT on the Mac has a different include. To include GLUT in a project for the mac, you must use the following:

#include <GLUT/glut.h>

and not:

#include <GL/glut.h>

In order to cut code that will compile successfully on either platform we can use optional includes with the #ifdef, #else and #endif preprocessor directives. Props to “kainjow” for providing this information in his/her forum post. Here’s how:

#ifdef __APPLE__
#include <GLUT/glut.h>
#include <GL/glut.h>

All this does is say “if we’re running on an Apple machine, include GLUT/glut.h, otherwise include GL/glut.h. Now to actually learn OpenGL/GLUT…

Apple Support FTW!

I just wanted to give a shout out to Apple customer support. My Macbook Pro recently started powering off without warning while the OS was still reporting 30-50% battery remaining. As it’s still under an extended warranty through David Jones (i.e. not Apple care), it went to The Mac Doctors for an appraisal. They reported it was a battery fault, which understandably, my extended warranty doesn’t cover. The Mac Doctors also asked Apple if they’d come to the party and replace it for me, given that the battery had only cycled 59 times (apparently after 250 cycles is when you should expect your battery to be dead) and it wasn’t a straight forward case of not holding charge. Apple declined to come to the party when asked by The Mac Doctors, however The Mac Doctors advised me to call Apple personally and explain myself. Taking their advice, I called Apple. After a brief conversation with a general support guy, I was put on hold for a bit (not too long) before I was forwarded to a product specialist. After confirming some details about the battery, as well as explaining that I’d installed any updates from Apple, the product specialist informed me that my battery was prone to failure more often than it should. He then went on to say that becuase I updated regularly, the only explanation was a somewhat known hardware failure, which meant Apple would replace the battery for me.

In addition to the excellent outcome, both of the support guys I spoke to were very professional, polite and patient. As well as Apple support being excellent, The Mac Doctors must also be given “mad props” for going to the trouble of asking Apple to cover the battery, and then advising me to talk to them myself. So to everyone involved, thank you muchly, and well done.