1
Known problems fixed in GtkAda 1.2.11/1.3.11
3
- Declaring new signals for widgets with a common parent
4
Problem: When declaring new signals (with Initialize_Class_Record) for
5
two widget types that extend the same Gtk parent, the first one
6
is not taken into account and the signal is not accessible.
7
Workaround: Declare a first child of the Gtk parent, and make the two other
8
widgets inherit from it. Declare the signals for this first
11
- Option menus not shown properly when using the GUI builder
12
Problem: When creating option menus using the GUI builder, gate would
13
not generate a code that would display the option menu items
15
Workaround: Modify the generated code by hand, adding explicitely calls
16
to Show (The_Menu_Item).
18
- Callbacks with same name not handled correctly by Gate
19
Problem: Callbacks with the same name in different top level widgets
20
in the XML file were not duplicated in each callbacks package.
21
Workaround: Use unique name among the project, or modify the generated code
24
- Connecting signals with Object_Connect might raise CE later on
25
Problem: When you connect a signal to object A with object_connect,
26
passign object B as the slot object, it might happen than B
27
is destroyed but not A. The next time the signal is emitted, you
28
will get a Constraint_Error, since B no longer exists
29
Workaround: Connect the "destroy" event to object B, so as to automatically
30
disconnect the first signal when B is destroyed. This is now
31
done automatically by GtkAda
b'\\ No newline at end of file'