Revision 6d1ef619baf3d738285880ef745ddd512d6e97bb

[Sean Egan]

On 6/22/07, Etan Reisner <pidgin at unreliablesource.net> wrote:
> Right, and I'm trying to understand for what purpose the ui needs to know
> that information. It would seem to me that neither filling in fields
> correctly or automatically connecting would need that (though auto-filling
> might be made easier that way).

You don't think the UI should know if clicking "Register" succeeded or not?

> Wouldn't it be just as effective to add a
> purple_account_registered(PurpleAccount *account, gboolean success)
> function to account.h and a corresponding ui_op? Which would be a minor
> bump, right? Also adding a corresping account-registered signal, so that
> plugins and other places can respond to it.

All three of those options were discussed. Andy's original plan was to
use a ui_op (or maybe it was a prpl_op, but a ui_op would be better).
I was originally hesitant to use up one of those precious
purple_reserved padding pointers, but upon reflection, I think that's
a better idea now.

-s.