Mercurial > pidgin
view .cvsignore @ 11217:f854402837ba
[gaim-migrate @ 13349]
The history plugin really should require logging be on. Otherwise, you can end up seeing a really old conversation instead of the "last" conversation. I've made this change.
Now, the history plugin can't be silently failing to do its job if logging is disabled. I've coded it to display a warning dialog under the following conditions:
1) The user enables the history plugin and neither IM nor chat logging is enabled.
2) The user starts Gaim with the history plugin and no logging enabled.
3) The user disables logging while the history plugin is enabled.
I thought about automatically disabling the history plugin after displaying the dialog, but I imagine (hope?) people will enable the history plugin, see the dialog, and enable logging. If this is what happens, they would be confused if the history plugin automatically disabled itself when it displayed the dialog.
This should address RFE 1241878, "History plugin should have a more helpful description".
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Tue, 09 Aug 2005 05:20:07 +0000 |
parents | c398f55ce5c7 |
children | b0ad08e1d492 |
line wrap: on
line source
config.h libtool config.status intl ABOUT-NLS compile config.guess config.sub Doxyfile ltconfig ltmain.sh install-sh missing aclocal.m4 configure config.h.in stamp-h.in Makefile.in config.log config.cache Makefile stamp-h gaim.spec depcomp stamp-h1 autom4te*.cache configure.2.1x confdefs.h *.swp win32-install-dir .temp-gettextize m4 gaim.pc *.apspec