Better scope in GAsyncReadyCallback/GDestroyNotify
authorJohan Dahlin <johan@gnome.org>
Wed, 25 Nov 2009 00:18:27 +0000 (22:18 -0200)
committerJohan Dahlin <johan@gnome.org>
Wed, 2 Dec 2009 12:31:29 +0000 (10:31 -0200)
commitf74823dbcb647dee950c066119876db9f0edc32f
tree94d6434eb856fe04182b6252d0102895ca12625d
parent8ebaa58148917ce2b89b68f00aefbdca3eac87fd
Better scope in GAsyncReadyCallback/GDestroyNotify

GAsyncReadyCallback should have use the async scope per
default and GDestroyNotify should be notified if the
previous parameters are a callback and user data.

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=602862
giscanner/annotationparser.py
tests/scanner/Makefile.am
tests/scanner/annotation-1.0-expected.gir
tests/scanner/annotation-1.0-expected.tgir
tests/scanner/foo-1.0-expected.gir
tests/scanner/foo-1.0-expected.tgir
tests/scanner/foo.h
tests/scanner/utility-1.0-expected.gir
tests/scanner/utility-1.0-expected.tgir