Incompatibility between iPhoto 06, KA, and Adium

An instant messenger which can connect to AIM, GTalk, Jabber, ICQ, and more.
Post Reply
nanu
Harmless
Posts: 4
Joined: Mon May 02, 2005 4:30 pm

Incompatibility between iPhoto 06, KA, and Adium

Post by nanu »

Ok, this is going to be quite longwinded but please bear with me...

Short Version:
There's a plugin for iPhoto called Keyword Assistant that makes adding keywords to pictures a lot easier. It really is an awesome plugin. Unfortunately, I think it causes a bug when trying to initiate a file transfer with an MSN contact by dragging and dropping from iPhoto.


Long Version:
I'm using AdiumX 0.88, iPhoto 6.0 and Keyword Assistant 1.9 on OS 10.4.4.
When attempting to initiate a file transfer with a contact on MSN, I drag and drop a photo from within iPhoto into the message area in the Adium chat window. The preview of the photo appears but when i press return the file transfer window doesn't appear and the contact isn't notified that there is a transfer for them to accept.
If I open up the file transfer window manually, the file is listed there but it's status is initiating the transfer. Cancelling this transfer doesn't work and Adium has to be restarted for the listing to disappear.

After getting several other people to try and start transfers in the same way and them not having any problems, I realised that the major difference to our systems was the presence of Keyword Assistant on mine.
After uninstalling KA, the drag and drop initiated file transfer from within iPhoto works as expected, with the file transfer window appearing and the contact being prompted to accept the file.


Summary:
Am I completely wrong in assuming KA is the culprit?
Does anyone else have iPhoto, KA and Adium running without this problem?
What can I do to provide the developer of KA with as much information as possible so as to make this bug easier to fix?
User avatar
The_Tick
Cocoaforge Admin
Posts: 4642
Joined: Thu Dec 02, 2004 6:06 am
Contact:

Post by The_Tick »

It's an input manager, so it affects every single application that uses input managers. This is their problem, you need to contact them
User avatar
evands
Cocoaforge Admin
Posts: 3152
Joined: Thu Dec 02, 2004 10:55 pm
Location: Decatur, GA
Contact:

Post by evands »

Just ask Ken to drop me a line and include the information you figured out about the problem to get the ball rolling. :)
The duck still burns.
--
My company: Saltatory Software. Check it out :)
Post Reply