Opened 12 years ago

Closed 12 years ago

#11007 closed defect (fixed)

Idle status should not bleed through a meta contact

Reported by: zacw Owned by: evands
Milestone: Adium 1.4 Component: Adium UI
Version: Severity: normal
Keywords: Cc:
Patch Status:


A meta contact such as:

  • Available
  • Idle, away
  • Available

Should not be shown as available with an idle time.

Change History (6)

comment:1 Changed 12 years ago by Evan Schoenberg

On the other hand, what about the case where I have a metacontact with an AIM contact and a Facebook contact? Facebook doesn't support the concept of idleness, so an idle metacontact would permanently appear available.

comment:2 Changed 12 years ago by Zachary West

I think that's not our problem. Ignoring facebook there's really no case where you would want the non-preferred contact's information. I think changing the propertyForKey:.. methods to only check the preferred contact might be a nice, and very clean, solution.

comment:3 Changed 12 years ago by Evan Schoenberg

If a metacontact were to behave only as a proxy to its preferred contact, rather than consolidating information, except for in the Get Info window, that would actually cut out a ton of code from AIMetaContact, as we wouldn't have to maintain any sort of status cache, resolve conflicting information, etc.

The disadvantage would be that a status message would only show up if the preferred contact has it.... but almost all services supports modern status messages now that MSN has personal messages, so it's probably okay.

comment:4 Changed 12 years ago by Zachary West

I think consolidating information should be left to inspector visual stuff -- i.e., the tooltip or get info window. Otherwise let the meta contact act merely as the proxy.

comment:5 Changed 12 years ago by Evan Schoenberg

Owner: changed from nobody to Evan Schoenberg
Status: newassigned

Works for me.

comment:6 Changed 12 years ago by Evan Schoenberg

Resolution: fixed
Status: assignedclosed

(In [25383]) AIMetaContact now displays properties only for its preferred contact. This cleans up a fair amount of code and provides a more intuitive behavior in many cases. Fixes #11007

Note: See TracTickets for help on using tickets.