File: known-problems-3.14

package info (click to toggle)
libgtkada 21.0.0.785f3cf4-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 41,160 kB
  • sloc: ada: 203,114; xml: 8,403; python: 4,501; perl: 3,838; ansic: 2,949; sh: 2,851; makefile: 351; objc: 160; javascript: 100
file content (75 lines) | stat: -rw-r--r-- 3,046 bytes parent folder | download | duplicates (3)
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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
===============================
Known problems in GtkAda 3.14.x
===============================

Copyright (C) 2015-2016, AdaCore

The following is a listing of known problems in GtkAda 3.14.x
Each entry contains a status line stating when the problem was fixed, and on
which release(s). In addition, any wavefront issued subsequent to the date
specified (in ISO format YYYY-MM-DD) also contains the fix. This can be used
to determine if a given release or wavefront has the fix identified in the
entry.

Note that older releases might or might not be affected by the problems listed
in this document.

Known problems fixed in GtkAda 17.0
-----------------------------------

KP-314-P411-032 Unable to launch glade

  Problem:    The glade executable does not launch, with messages of the form
              Unable to load image (Failed to open file
               '<some_path>/install/share/glade/pixmaps/plus.png':
                No such file or directory)

  Status:     This was fixed in GtkAda 17.0

  Workaround: Create a symlink from your GtkAda install to <some_path>.

KP-314-OC10-015 Memory leaks in *_foreach

  Problem:    In some cases, gtk+ functions accept some user data, but do not
              provide a way to know when it can be freed. This resulted in
              memory leaks. In some cases, we could fix the binding by freeing
              the no-longer needed user data. However, some functions no
              longer have a binding, since that would always lead to memory
              leaks. Here is the full list:
                 gtk.accel_group.find_user_data
                 gtk.builder.connect_signals_full_user_data
                 gtk.clipboard.request_contents_user_data
                 gtk.clipboard.request_image_user_data
                 gtk.clipboard.request_rich_test_user_data
                 gtk.clipboard.request_targets_user_data
                 gtk.clipboard.request_text_user_data
                 gtk.clipboard.request_uris_user_data
                 gtk.main.key_snooper_install_user_data
                 pango.attributes.filter_user_data

  Status:     This was fixed in GtkAda 17.0

  Workaround: If you were using these functions, consider storing the user
              data in a new tagged type derived from the widget. Most of the
              time this should be applicable.

KP-314-OB27-029 GtkProgressBar CSS styling not working

  Problem:    The -GtkProgressBar-min-horizontal-bar-height and
              -GtkProgressBar-min-vertical-bar-width CSS properties are not
              taken into account with Gtk 3.14 version. Hard-coded default
              values are used instead to define the progress bar's size, making
              it thin by default.

  Status:     This was fixed in GtkAda 17.0

  Workaround: None known.

KP-314-OB19-053 Wrong binding for Gtk.Tree_Store.Remove

  Problem:    The binding for this function set Iter to null, instead of
              setting it to a valid iter.

  Status:     This was fixed in GtkAda 17.0

  Workaround: None known.