Adium

Ticket #2661 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

status badge / status from old versions

Reported by: anonymous Owned by: nobody
Milestone: Component: Adium UI
Version: 1.0svn Severity: normal
Keywords: Cc:
Patch Status:

Description

the new status logo (combined version) is really nice :-) best combination possible i think. (the duck including the status icon).

but there is another problem (i updated from 0.87). in the menu below the status bagde there are show the "default" status things like "invisible, not available" and the user defined away messages like "i am currently not at home" or something.

the problem is, that this old (v.0.87) status is not shown in the adium preferences so.. you cant remove or edit it.

Attachments

v0.87_prefs_correct.jpg (43.9 KB) - added by anonymous 4 years ago.
this is how it looks in v0.87 (correct)
v1.0svn_correct.jpg (16.1 KB) - added by anonymous 4 years ago.
correctly shown in the 1.0svn status menu
v1.0svn_prefs_status_missingjpg.jpg (39.1 KB) - added by anonymous 4 years ago.
but missing in the 1.0svn preferences... not able to delete/modify the "pre 1.0 status"

Change History

Changed 4 years ago by evands

What old status is not shown in the preferences? Invisible is now always shown beneath Away, if that's what you mean. Screen shots of the menu and of the preferences might be appropriate.

Changed 4 years ago by anonymous

this is how it looks in v0.87 (correct)

Changed 4 years ago by anonymous

correctly shown in the 1.0svn status menu

Changed 4 years ago by anonymous

but missing in the 1.0svn preferences... not able to delete/modify the "pre 1.0 status"

Changed 4 years ago by anonymous

Hi Evan,

i uploaded the images. Anything else i can help with?

Changed 4 years ago by evands

  • status changed from new to closed
  • resolution set to fixed

Localized nibs were broken for the status preferences. It's been fixed. If you see really weird behavior like this in 1.0svn, I recommend switching to running in English temporarily and verifying it's not an issue with localization -- pointing out that the problem only occurs in your language will narrow it down rapidly.

Note: See TracTickets for help on using tickets.