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.98.70.143 with SMTP id o15mr14168136pfi.10.1448316760431;
        Mon, 23 Nov 2015 14:12:40 -0800 (PST)
X-Received: by 10.182.87.132 with SMTP id ay4mr331129obb.14.1448316760395;
 Mon, 23 Nov 2015 14:12:40 -0800 (PST)
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!mv3no1516411igc.0!news-out.google.com!l1ni6830igd.0!nntp.google.com!mv3no938303igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 23 Nov 2015 14:12:40 -0800 (PST)
In-Reply-To: <09fb4ec5-ec82-40d3-968e-d2d9b06e4c19@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=217.128.107.241;
 posting-account=O3LyFwoAAACc1uh60ZcOUmAGdDmGsEcV
NNTP-Posting-Host: 217.128.107.241
References: <a9594ffb-7548-48f5-9e77-0230202a5aa5@googlegroups.com>
 <5f76d6a8-f733-4f36-89df-56eefcd795f8@googlegroups.com>
 <33bdc708-11fa-4091-8569-9436397e1695@googlegroups.com>
 <c9e7fb9b-e85f-4f74-b378-af7a588527a2@googlegroups.com>
 <cd1528e0-f028-45b4-8a41-0b7eb19ac8de@googlegroups.com>
 <09fb4ec5-ec82-40d3-968e-d2d9b06e4c19@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ffca4197-80bc-4a4e-9e8e-4480e0a63f5b@googlegroups.com>
Subject: Re: Gnoga Callback Handlers with user data
From: slos <new.stephane.los@gmail.com>
Injection-Date: Mon, 23 Nov 2015 22:12:40 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:28512
Date: 2015-11-23T14:12:40-08:00
List-Id: <comp.lang.ada>

Le lundi 23 novembre 2015 18:24:48 UTC+1, David Botton a =E9crit=A0:
> > Well, that's what I would like to achieve but cannot figure out how.
> > Since what I get in the handler is the whole UI data, how can I figure =
out which element has triggered the event ?
>=20
> Ok so given the code you posted.
>=20
> if Object.Unique_ID =3D App.My_Button.Unique_ID
>=20
> if Object.Unique_ID =3D App.My_Exit.Unique_ID
>=20
> David Botton

OK, got it ! I shouldn't try to understand anything this late...
Well, since I cannot associate the access to the object that shall handle t=
he click event as some user data, I have to set up some map to associate ID=
 or Unique_ID to those object accesses because I don't want to check the ID=
s in a big if then else or case.
Thanks for your explanations.

St=E9phane