view plugins/gaim.pl @ 4849:adf9ca39578f

[gaim-migrate @ 5174] Christian, I got the following backtrace after opening and closing some convos: #4 <signal handler called> #5 0x08066e47 in gaim_window_get_active_conversation (win=0x82b44d8) at conversation.c:775 #6 0x08085599 in update_send_as_selection (win=0x82b44d8) at gtkconv.c:1964 #7 0x4067fa4c in g_timeout_dispatch () from /usr/lib/libglib-2.0.so.0 So although I couldn't reproduce it, I guess it's still possible for Gaim to crash there. This fixes that by making sure that win still exists before it tries to update the send as menu for it. The other way to fix this would be to keep track of the g_timer thingy and then remove it when destroying win. I don't know which was is better. Probably the other way. committer: Tailor Script <[e-mail]>

sub description {
        my($a, $b, $c, $d, $e, $f) = @_;
        ("Example", "1.0", "An example Gaim perl script that does nothing particularly useful:\n\t-Show a dialog on load\n\t-Set user idle for 6,000 seconds\n\t-Greets people signing on with \"Hello\"\n\t-Informs you when script has been loaded for one minute.", "Eric Warmenhoven <eric\@warmenhoven.org>", "http://gaim.sf.net", "/dev/null");
}

$handle = GAIM::register("Example", "1.0", "goodbye", "");

GAIM::print("Perl Says", "Handle $handle");
		
$ver = GAIM::get_info(0);
@ids = GAIM::get_info(1);

$msg = "Gaim $ver:";
foreach $id (@ids) {
	$pro = GAIM::get_info(7, $id);
	$nam = GAIM::get_info(3, $id);
	$msg .= "\n$nam using $pro";
}


GAIM::command("idle", 6000);

GAIM::add_event_handler($handle, "event_buddy_signon", "echo_reply");
GAIM::add_timeout_handler($handle, 60, "notify");

sub echo_reply {
	$index = $_[0];
	$who = $_[1];
	GAIM::print_to_conv($index, $who, "Hello", 0);
}

sub notify {
	GAIM::print("1 minute", "gaim test has been loaded for 1 minute");
}

sub goodbye {
	GAIM::print("You Bastard!", "You killed Kenny!");
}