custom status window always defaults to auto-reply

[stillm]

I'm not sure if this is a bug, or if it is intentional, but whenever I try to create a custom status, Adium always defaults to Auto-reply. I never use auto-reply, and never want to use it, so the fact that it always defaults to this is very frustrating (it means I need to uncheck that box every single time I create an away message). Is there a way to allow the user to either set a default auto-reply behavior for the custom status window, or else can Adium default to whichever option (auto-reply or not) that the user selected the last time they created a custom status?

[jas8522]

This is fixed in 1.1svn (probably 1.0.2, but perhaps for 1.0.3 when it comes out).

When I choose custom status, none of the boxes are checked by default.

[miknight]

Thanks, I have checked the plist files and they have correct permissions and other things are being remembered properly.

Adium will remember the checkbox status as long as I do not set my status to 'Available' before or after quitting and re-launching it, unless I choose another custom status after the second launch before choosing 'Available'.

Here are steps for showing that it does remember the checkbox setting if the status is not set to 'Available':

1. Launch Adium,
2. choose 'Custom...' status,
3. uncheck the Auto-reply checkbox,
4. click OK,
5. quit Adium,
6. launch Adium,
7. check the custom status window.

The custom status window will show the auto-reply checkbox unchecked, which is good behaviour as expected.

However, if you replace the final step in that list with:

7. set status to 'Available',
8. check the custom status window.

The custom status window will have the auto-reply checkbox checked, which is incorrect behaviour.

I hope this helps other people reproduce it! I didn't realise there was such subtlety to the problem until I spent a good 10 mins narrowing it down just now.

[jas8522]

Again, I cannot reproduce this while following those exact steps (with the second #7 and 8 of course) with 1.1.4 or 1.2svn

You haven't specified whether or not you actually tried a fresh set of preferences - you just said that you checked the permissions. It never hurts to try ;) It could be that the box checked was a default way back when and since the plist is set so, it won't change until you get a fresh set of plists... I don't believe Adium will generate only one preference file - you will likely need to have it generate an entire set, then just copy the important stuff back in.

[miknight]

Stale preference files seemed like a probably cause. Just to be safe I completely backed-up/removed my ~/Library/Application Support/Adium 2.0 directory and launched a fresh 1.1.4 just with my MSN account, following steps 1 to 8 above. Unfortunately I am still experiencing the problem.

Are there any other preference files I should be know about besides the ones in that directory?

[jas8522]

miknight: not that I'm aware of.

[jas8522]

This should be solved for 1.2.2 in [22538]

[miknight]

It is fixed now :) Thank you.

[darkrain42]

This seems to have popped up again. It occurs for me in 1.3.3.

[darkrain42]

This is still occuring for me in 1.4hgr2274. Re-open?

[jas8522]

This was also occurring for me with a set of very old preferences - try it with a fresh set and see if you can reproduce it before we possibly frivolously re-open this.

[darkrain42]

I can recreate it after removing com.adiumX.adiumX.plist (hey, that looks like another X to get rid of...and renamed to im.adium.adium.plist or something ;) ) and the Application Support/Adium 2.0 folder.

Did I miss a plist I should have moved out of the way?

[darkrain42]

*poke*

[Zachary West <zacw@…>]

(In  9c32a9b78f76) Revert the "never use last saved status" behavior. Re-fixes #6227.

The behavior was #ifdef'd out to appease MSN users, who wanted their status messages to propagate. Find some middle ground here: if a status message is currently set, a custom new-status window will retain it. Otherwise, it'll use the saved one. And we'll always use the last-saved status settings otherwise, so "autoreply" saving always works.