In Pidgin, display a full date on the timestamp of the first message to

cross the boundary into a new day.  Sean and various users want this.  I
think I'm finally going to admit it's a decent idea.

I've also refactored plenty of code related to the conversation-timestamp
and log-timestamp signals.  This breaks API compatibility, but I'm pretty
sure the only plugin that uses those signals is the Message Timestamps
plugin that we ship.  The changes eliminate duplicated code between the
core/UI and the plugin.

1 files changed, 32 insertions, 0 deletions

diff --git a/libpurple/signals.c b/libpurple/signals.c
index 97023f709c..eee418ba92 100644
--- a/libpurple/signals.c
+++ b/libpurple/signals.c
@@ -976,6 +976,38 @@ gaim_marshal_POINTER__POINTER_INT64(
 }
 
 void
+gaim_marshal_POINTER__POINTER_INT_BOOLEAN(
+                                    GaimCallback cb, va_list args, void *data,
+                                    void **return_val)
+{
+	gpointer ret_val;
+	void *arg1 = va_arg(args, void *);
+	gint arg2 = va_arg(args, gint);
+	gboolean arg3 = va_arg(args, gboolean);
+
+	ret_val = ((gpointer(*)(void *, gint, gboolean, void *))cb)(arg1, arg2, arg3, data);
+
+	if (return_val != NULL)
+		*return_val = ret_val;
+}
+
+void
+gaim_marshal_POINTER__POINTER_INT64_BOOLEAN(
+                                    GaimCallback cb, va_list args, void *data,
+                                    void **return_val)
+{
+	gpointer ret_val;
+	void *arg1 = va_arg(args, void *);
+	gint64 arg2 = va_arg(args, gint64);
+	gboolean arg3 = va_arg(args, gboolean);
+
+	ret_val = ((gpointer(*)(void *, gint64, gboolean, void *))cb)(arg1, arg2, arg3, data);
+
+	if (return_val != NULL)
+		*return_val = ret_val;
+}
+
+void
 gaim_marshal_POINTER__POINTER_POINTER(GaimCallback cb, va_list args, void *data,
                                       void **return_val)
 {