[544]=>Good morning
 [543]=>You know the fee...
 [542]=>Date more, care ...
 [541]=>Moving On



February 2020
sun mon tue wed thu fri sat
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29


 [RAndoMness]=> 28Sep09
 [JPsDocs] => 22Feb09
 [JPics] => 10Dec11

recent music
Boycott SONY


  getentry(426); getentry(428);

An imaginary tech support call
added Mon September 19 2005 at 7:06 PM
I would never have actually called any tech support for the problem, but I did come pretty close to writing a stinging diatribe against iTunes crying out about the abuse of keyboard shortcuts.

My computer started acting up. For some reason, Firefox was crashing pretty bad. I wasn't horribly surprised, considering all the problems I'd had getting the internet to work in the first place (I *still* don't know why I was having troubles connecting). I killed firefox and opened up Internet Explorer. Hey! I was in the middle of looking for an extremely important answer. I did not want to wait for firefox to decide to find itself. Actually, I don't even remember what I was working on, but I looked down a couple minutes later and saw iTunes open. "Hmm," I thought, "I don't remember openning iTunes." I cranked up some tunes and continued on my aimless pursuit of whatever the heck it is I do on my computer (I think I was sorting through emails at the time).

I was about to write my first entry for a long time and in the process, I was going to select a paragraph of text. Because the mouse is sitting on the table in front of me and the keyboard is on my lap, I naturally began to use keyboard shortcuts to highlight characters. And I lost my music. So I switched to iTunes and the volume was turned down. Hmmm. Very fishy indeed.

I fiddled some more and found that ctrl+shift+down muted iTunes. I glanced through iTunes' settings, but don't see any options for keyboard accelerators, so I hop on googleand sure enough, I find that the shortcut to toggle the mute in iTunes is ctrl+shift+down. Oh man, that really gets me. I would've probably uninstalled iTunes on the spot if I had installed the update like it wanted me to when I first openned it up. That kind of behavior is simply unacceptable, especially since further fiddling revealed that ctrl+shift+up was launching iTunes. If programs start hijacking my keyboard shortcuts that are clearly given to other programs, all bets are off.

Imagine for a moment if I'd called iTunes tech support, or even worse, Dell or Gateway tech support at this point. All they have is my word that this strange behavior is happening, and I'm *fuming*. I'll leave the exact words of the call as an exercise for the ambitious reader.

In a fit of rationality, I decided to see if I could reproduce this behavior in multiple programs. As I said earlier, if I'd installed the update already, I probably wouldn't have gotten this far. AIM happened to be open in the background, so I switched to it and tried again.

Hmmm... Doesn't seem to work there. Maybe the problem's not with iTunes *after* all. Could it be... *gasp* FireFox?had my beloved somehow turned on me?

Well, yes and no. it wasn't *totally* because of FireFox, it was actually a feature of one of my installed add-ons. In the defense of FoxyTunes, it's a very sensible feature for a program that is made to control external music programs to install keyboard shortcuts to control them. Somehow I'd simply overlooked the feature every time I've used it before. Perhaps mostly because my keyboarding habits at work are seeping into my personal life (I do a lot more text editing at work, because, well, I'm a programmer).

At any rate, for a variety of reasons, the poor fellows of tech support were spared a very confusing tech support call about a "bug" that turned out to be a feature of a third-part add-on to a program that is completely unrelated to the original complaint. And I *still* don't know why my internet wasn't working.

stephen says:
as per our conversation today...

<i>Itunes is the devil</b>
posted Sat September 23 2006 at 1:58 PM

Jo-Pete Nelson says:
And you can't <i>nest tags</b> properly, so why should I listen to you?:P
posted Sat September 23 2006 at 1:58 PM

Jo-Pete Nelson says:
Ouch... that hurts... looks like it's a bug. I thought that I allowed nested tags, but apparently I don't...

Oh well. v2.0...
posted Sat September 23 2006 at 1:58 PM


Allowable HTML:
<a href="">links</a>
Comment guidelines