summaryrefslogtreecommitdiff
path: root/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page
diff options
context:
space:
mode:
Diffstat (limited to 'tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page')
-rw-r--r--tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page11
1 files changed, 11 insertions, 0 deletions
diff --git a/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page b/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page
index fee97a4e..200167fa 100644
--- a/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page
+++ b/tests/doctool/GIRepository-2.0-Python-expected/GIRepository.Repository.find_by_gtype.page
@@ -35,4 +35,15 @@ the type must first have been loaded. There is currently no
mechanism for determining the namespace which corresponds to an
arbitrary GType - thus, this function will operate most reliably
when you know the GType to originate from be from a loaded namespace.</p>
+
+<table>
+<tr>
+<td><p>gtype :</p></td>
+<td><p>GType to search for</p></td>
+</tr>
+<tr>
+<td><p>Returns :</p></td>
+<td><p><link xref="GIBaseInfo">GIBaseInfo</link> representing metadata about @type, or %NULL</p></td>
+</tr>
+</table>
</page>