comp.lang.ada
 help / color / mirror / Atom feed
* Gtl-Critical
@ 2016-06-26  7:11 ldries46
  2016-06-26  8:10 ` Gtl-Critical mockturtle
  2016-06-26  8:38 ` Gtl-Critical Dmitry A. Kazakov
  0 siblings, 2 replies; 3+ messages in thread
From: ldries46 @ 2016-06-26  7:11 UTC (permalink / raw)


When starting an program with GtkAda I do get the following messages

(template.exe:13728): Gtk-CRITICAL **: gtk_main_quit: assertion 'main_loops 
!= NULL' failed

(template.exe:13728): Gtk-CRITICAL **: gtk_widget_grab_default: assertion 
'gtk_widget_get_can_default (widget)' failed

(template.exe:13728): Gdk-CRITICAL **: inner_clipboard_window_procedure: 
assertion 'success' failed

(template.exe:13728): Gdk-CRITICAL **: inner_clipboard_window_procedure: 
assertion 'success' failed

Is this a problem in gtk ada or do do something wrong The program a template 
for future development is running correctly as far as I see.
The first two messages appear almost immediate the last two after some time, 
but I the only thing I did in the mean time was shifting the window to 
another position on the screen.

L. Dries 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Gtl-Critical
  2016-06-26  7:11 Gtl-Critical ldries46
@ 2016-06-26  8:10 ` mockturtle
  2016-06-26  8:38 ` Gtl-Critical Dmitry A. Kazakov
  1 sibling, 0 replies; 3+ messages in thread
From: mockturtle @ 2016-06-26  8:10 UTC (permalink / raw)


On Sunday, June 26, 2016 at 9:12:17 AM UTC+2, ldries46 wrote:
> When starting an program with GtkAda I do get the following messages
> 
> (template.exe:13728): Gtk-CRITICAL **: gtk_main_quit: assertion 'main_loops 
> != NULL' failed
> 
> (template.exe:13728): Gtk-CRITICAL **: gtk_widget_grab_default: assertion 
> 'gtk_widget_get_can_default (widget)' failed
> 
> (template.exe:13728): Gdk-CRITICAL **: inner_clipboard_window_procedure: 
> assertion 'success' failed
> 
> (template.exe:13728): Gdk-CRITICAL **: inner_clipboard_window_procedure: 
> assertion 'success' failed
> 
> Is this a problem in gtk ada or do do something wrong The program a template 
> for future development is running correctly as far as I see.
> The first two messages appear almost immediate the last two after some time, 
> but I the only thing I did in the mean time was shifting the window to 
> another position on the screen.
> 
> L. Dries

I am not an expert about Gtk at all, but errors that look like this happen almost always when starting a Gtk application.  They seem to be harmless enough, tough, since the application still works nicely... 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Gtl-Critical
  2016-06-26  7:11 Gtl-Critical ldries46
  2016-06-26  8:10 ` Gtl-Critical mockturtle
@ 2016-06-26  8:38 ` Dmitry A. Kazakov
  1 sibling, 0 replies; 3+ messages in thread
From: Dmitry A. Kazakov @ 2016-06-26  8:38 UTC (permalink / raw)


On 2016-06-26 09:11, ldries46 wrote:
> When starting an program with GtkAda I do get the following messages
>
> (template.exe:13728): Gtk-CRITICAL **: gtk_main_quit: assertion
> 'main_loops != NULL' failed
>
> (template.exe:13728): Gtk-CRITICAL **: gtk_widget_grab_default:
> assertion 'gtk_widget_get_can_default (widget)' failed
>
> (template.exe:13728): Gdk-CRITICAL **: inner_clipboard_window_procedure:
> assertion 'success' failed
>
> (template.exe:13728): Gdk-CRITICAL **: inner_clipboard_window_procedure:
> assertion 'success' failed
>
> Is this a problem in gtk ada or do do something wrong The program a
> template for future development is running correctly as far as I see.
> The first two messages appear almost immediate the last two after some
> time, but I the only thing I did in the mean time was shifting the
> window to another position on the screen.

These look like bugs in Windows GTK caused by incompatibilities 
introduced in GTK 3.x.

It is certainly so for gtk_widget_get_can_default. This bug is in the 
dialog boxes which do not set Can_Default on any of their buttons. God 
knows why this is necessary and why this is "critical". GTK dialog boxes 
are in general broken, but you can work around of most of the problems.

For others I cannot tell for sure. Add tracing to you program to 
identify the place where the error message appear. Then you could figure 
out how to deal with that.

Remember, each new version of GTK introduces new bugs and 
incompatibilities. You cannot assume that any part of old code would work.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-06-26  8:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-26  7:11 Gtl-Critical ldries46
2016-06-26  8:10 ` Gtl-Critical mockturtle
2016-06-26  8:38 ` Gtl-Critical Dmitry A. Kazakov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox