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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.176.4.110 with SMTP id 101mr8681216uav.11.1461829714570;
        Thu, 28 Apr 2016 00:48:34 -0700 (PDT)
X-Received: by 10.182.226.4 with SMTP id ro4mr175844obc.2.1461829714501; Thu,
 28 Apr 2016 00:48:34 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!88no1030499qga.1!news-out.google.com!uv8ni120igb.0!nntp.google.com!i5no332160ige.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 28 Apr 2016 00:48:34 -0700 (PDT)
In-Reply-To: <nfps27$1lko$1@gioia.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=2a02:2ab8:224:1:84ea:b257:7f8d:aaa7;
 posting-account=6yLzewoAAABoisbSsCJH1SPMc9UrfXBH
NNTP-Posting-Host: 2a02:2ab8:224:1:84ea:b257:7f8d:aaa7
References: <do4ph6Fa6ghU1@mid.individual.net> <nfkhm1$18de$1@gioia.aioe.org>
 <do68anFkub2U1@mid.individual.net> <nfl0pa$23u$1@gioia.aioe.org>
 <0a9cf35e-45ba-49c1-9d6a-4a0da3457e70@googlegroups.com>
 <do8k0uF8ojjU1@mid.individual.net>
 <31e4394b-eb85-4d31-bd25-f2bd332c7c9b@googlegroups.com>
 <nfps27$1lko$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <39b5f02e-3b17-460b-99fa-e5ba9a0a6c7d@googlegroups.com>
Subject: Re: Where do I get my Cairo context from (in GTK3)?
From: briot.emmanuel@gmail.com
Injection-Date: Thu, 28 Apr 2016 07:48:34 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: news.eternal-september.org comp.lang.ada:30311
Date: 2016-04-28T00:48:34-07:00
List-Id: <comp.lang.ada>

> End instances of widgets are never like that. The most frequent case is 
> a container widget handling signals from its children. The first 
> parameter of the handler is never ever used, because the identification 
> of the issuer is the handler procedure itself. The user parameter is the 
> container widget, which is the case for the OP, I suppose.

We are in agreement on that, but to me that's exactly what the "Slot"
parameter (or Object_Connect) is for (and that is exactly what we use
in GPS. I agree 100% that in most cases the widget that emits the event
is irrelevant in the handling of the signal.