Adium

Ticket #225 (closed defect: fixed)

Opened 5 years ago

Last modified 2 years ago

Idle preference not saved

Reported by: anonymous Owned by: nobody
Milestone: Adium 1.2.2 Component: Service/AIM
Version: 0.81 Severity: normal
Keywords: Cc:
Patch Status:

Description

Each time I relaunch the application, I have to redo my idle preferences. Namely, I choose not to let others know I am idle after X minutes, however everytime I restart the box is checked. Is there a way to have this preference saved?

Change History

Changed 5 years ago by catfish_man

  • milestone Adium X 0.81 deleted

Please don't set milestones when filing tickets

Changed 5 years ago by adamiser

This preference is indeed not working correctly.

Changed 5 years ago by anonymous

  • milestone set to Adium X 0.83

Changed 5 years ago by evands

  • cc evan.s@…, adam@… added

Can anybody reproduce this? I can't.

Changed 5 years ago by wootest

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

Changed 5 years ago by tick

  • status changed from closed to reopened
  • resolution worksforme deleted

Changed 5 years ago by wootest

  • status changed from reopened to closed
  • resolution set to worksforme

Changed 5 years ago by wootest

(The ticket was ostensibly opened because someone thought Adam had been able to reproduce it. However, he hadn't.)

Changed 5 years ago by catfish_man

  • milestone Adium X 0.83 deleted

Changed 4 years ago by klatt@…

  • status changed from closed to reopened
  • resolution worksforme deleted

This happens to me on tiger 10.4.2 and adium .84

Changed 4 years ago by tick

  • milestone set to Adium X 1.0

Setting to 1.0 for now, but we need to try to reproduce this or close it for good.

Changed 4 years ago by tick

  • field_haspatch set to 0

Can anyone get this to happen in .86 or svn head?

Changed 4 years ago by evands

  • status changed from reopened to closed
  • resolution set to worksforme
  • milestone Adium X 1.0 deleted

I really can't reproduce this. The status preferences are localized, so it could be a localization-specific issue. If you, theoretical bug reporting reader, reopen this because you have the problem in this ticket, please include the language in which Adium runs on your system.

Changed 4 years ago by evands

  • cc evan.s@…, adam@… removed

Changed 4 years ago by m@…

  • status changed from closed to reopened
  • resolution worksforme deleted

I am having this problem in 0.88 on the english version of 10.4.4. I set the idle time to 5 mins, then if I restart Adium it resets to 1 min.

Changed 3 years ago by evands

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

This really does work for me every time in 1.0 beta. If you are still seeing this issue, please describe precisely how you are changing the value and then what else you do before you quit adium.

Changed 3 years ago by phy1729

This happens to me also. I am Mac 10.4.9 Adium 1.0.4. When I open Adium, open prefs, go to the status tab, and set Let others know that I am idle after 5 min to 10. Then I close Adium and reopen the change is not saved. I went into the plist and changed it there and it has held. I have changed to 5 and back to 10 with no problems now.

Changed 2 years ago by evands

  • status changed from closed to reopened
  • patch_status set to None
  • resolution fixed deleted
  • pending set to 0
  • milestone set to Adium X 1.2.2

Changed 2 years ago by evands

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

(In [22539]) Don't use an NSNumber key in a dictionary which will be saved as a preference, as this prevents the entire preference group from saving; you must use an NSString. We now have logging which points the problem out.

Fixes #9082 (Custom status pre-population with previous message. Fixes #225 (yes, a ticket from 3 years ago!) which was previously very, very mysterious - the preference in question is in the same group as the last-status preference, which is why it wouldn't save.

Changed 2 years ago by evands

(In [22540]) Merged [22539]: Don't use an NSNumber key in a dictionary which will be saved as a preference, as this prevents the entire preference group from saving; you must use an NSString. We now have logging which points the problem out.

Fixes #9082 (Custom status pre-population with previous message. Fixes #225 (yes, a ticket from 3 years ago!) which was previously very, very mysterious - the preference in question is in the same group as the last-status preference, which is why it wouldn't save.

Note: See TracTickets for help on using tickets.