blob: 439bd57f6bf495195abeea464ef02dab1a700cc8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
<?xml version="1.0"?>
<page id="Regress.annotation_custom_destroy"
type="topic"
style="function"
xmlns="http://projectmallard.org/1.0/"
xmlns:api="http://projectmallard.org/experimental/api/"
xmlns:ui="http://projectmallard.org/1.0/ui/">
<info>
<link type="guide" xref="index" group="function"/>
<api:function>
<api:returns>
<api:type>none</api:type>
</api:returns>
<api:name>regress_annotation_custom_destroy</api:name>
<api:arg>
<api:type>Regress.AnnotationCallback</api:type>
<api:name>callback</api:name>
</api:arg>
<api:arg>
<api:type>Regress.AnnotationNotifyFunc</api:type>
<api:name>destroy</api:name>
</api:arg>
<api:arg>
<api:type>gpointer</api:type>
<api:name>data</api:name>
</api:arg>
</api:function>
</info>
<title>annotation_custom_destroy</title>
<synopsis><code mime="text/x-python">
@accepts(Regress.AnnotationCallback, Regress.AnnotationNotifyFunc, gpointer)
@returns(none)
def annotation_custom_destroy(callback, destroy, data):
# Python wrapper for regress_annotation_custom_destroy()
</code></synopsis>
<p>Test messing up the heuristic of closure/destroy-notification
detection, and fixing it via regress_annotations.</p>
<dl>
<dt><p>callback :</p></dt>
<dd><p>Destroy notification</p></dd>
<dt><p>destroy :</p></dt>
<dd></dd>
<dt><p>data :</p></dt>
<dd></dd>
</dl>
</page>
|
