Adium

Ticket #468 (closed defect: fixed)

Opened 3 years ago

Last modified 3 months ago

Growl Notification and Contact Alert Awayness

Reported by: spam@weks.net Assigned to: somebody
Priority: normal Milestone: Adium X 1.3
Component: Core Adium Version: 0.82
Severity: normal Keywords:
Cc: evan@adiumx.com Patch: None
Pending: 0

Description

I currently have the following set (and no others) on a user:

  • Contact returns from away
    • Display a Growl notification
    • Play the sound "..."
  • Contact signs on
    • Display a Growl notification
    • Play the shound "..."

When the user sets herself away, I get a Growl notification that she "is back." No.. no, she's not.

Change History

10/05/2005 09:39:17 PM changed by evands

  • milestone set to Adium X 0.86.

10/05/2005 09:39:36 PM changed by evands

Should confirm and fix if appropriate for 0.86

10/19/2005 08:34:43 PM changed by Diatribe

I have something similar happening, which sounds like the same problem.

1. I get a "returned from idle" right before a contact goes away.

2. I get a "contact came back" right before he signs off or goes away.

I get these events even though they are wrong and I get them independent of the event system used (i.e. Growl, sounds, etc.)

Oh, and it seems that #556 is a dupe of this.

11/10/2005 10:55:04 PM changed by tick

  • milestone changed from Adium X 0.87 to Adium X 1.0.
  • field_haspatch changed.

.8x is only for security issues now, moving to 1.0

12/03/2005 03:59:33 PM changed by cbarrett

  • cc set to evan@adiumx.com.
  • owner changed from anybody to cbarrett.

This sounds like an issue with the event coalescing. Evan, think you could find a couple minutes to explain that to me again?

12/03/2005 04:35:29 PM changed by evands

The OP's description doesn't sound like desired behavior at all -- the away event is being displayed as a returned event. Straight bug... haven't seen it myself. Does it really exist?

Diatribe's bug above sounds like it might be protocol-specific.. for example, if a contact can't be both idle and away and went from idle to away, perhaps idle is being cleared and then away set. The 'contact came back' is from the away status being cleared when the contact signs off... should be suppressed somehow.

And as far as the actual event coalescing which was supposed to be able to suppress a 'contact went away' in favor of the away message if possible... I'm not convinced it works at all, especially with the delay from AIM we have to deal with now ;)

12/03/2005 04:40:45 PM changed by cbarrett

There's a delay from AIM? And it's too bad that the coalescing doesn't work; that was a neat feature.

12/17/2005 01:50:36 AM changed by cbarrett

  • owner changed from cbarrett to somebody.

12/29/2005 11:15:31 PM changed by tick

  • status changed from new to closed.
  • resolution set to worksforme.
  • milestone deleted.

Can't duplicate, closing.

06/15/2008 12:50:23 PM changed by zacw

  • resolution changed from worksforme to fixed.

(In [23990]) Fix the world's most oddly placed bang, fixing a longstanding issue where the wrong event would fire for a contact. Fixes #468. Fixes #5551.

06/15/2008 12:52:47 PM changed by zacw

  • patch_status set to None.
  • pending changed.
  • milestone set to Adium X 1.3.

Nothing like the satisfaction of fixing your own 3 year old ticket.

06/15/2008 06:32:56 PM changed by zacw

(In [23997]) Fix the case of a metacontact which was available on connect going away causing the "come back" event to be fired. This would occur when the cache had a nil-entry and an event fires causing the cache to be updated before the meta contact is fully away, which triggers the "came back" event. Refs #468.

07/01/2008 05:15:23 PM changed by evands

(In [24152]) Backported [23997]: Fix the case of a metacontact which was available on connect going away causing the "come back" event to be fired. This would occur when the cache had a nil-entry and an event fires causing the cache to be updated before the meta contact is fully away, which triggers the "came back" event. Refs #468.

Backported [23990]: Fix the world's most oddly placed bang, fixing a longstanding issue where the wrong event would fire for a contact. Fixes #468. Fixes #5551.