From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Gtl-Critical
Date: Sun, 26 Jun 2016 10:38:23 +0200
Organization: Aioe.org NNTP Server
Message-ID: <nko4af$1gdd$1@gioia.aioe.org>
References: <576f8036$0$20643$e4fe514c@news.kpn.nl>
NNTP-Posting-Host: w/2xSGckQeJEFvqsQFNodA.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:30945
Date: 2016-06-26T10:38:23+02:00
List-Id: <comp.lang.ada>

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