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 X-Received: by 10.236.53.130 with SMTP id g2mr1508073yhc.31.1413253615814; Mon, 13 Oct 2014 19:26:55 -0700 (PDT) X-Received: by 10.182.28.10 with SMTP id x10mr12708obg.11.1413253615707; Mon, 13 Oct 2014 19:26:55 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!s7no2562296qap.0!news-out.google.com!rp1ni29760igb.0!nntp.google.com!h18no5585604igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 13 Oct 2014 19:26:55 -0700 (PDT) In-Reply-To: <32973087-dff1-4857-a7a6-1b39cb3ff4d2@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=66.176.73.77; posting-account=yiWntAoAAAC1KqC_shmxJYv07B9l6LNU NNTP-Posting-Host: 66.176.73.77 References: <13fb4505-4abd-4d5b-b18d-d05aa0a4dcb9@googlegroups.com> <32414aa2-3a0f-41fc-aef3-d8db709aacfc@googlegroups.com> <0b5ee58b-2d2d-4394-8215-0fa5d1a4740e@googlegroups.com> <5bf99c39-20f1-4fe3-9601-5c4d00598d7b@googlegroups.com> <32973087-dff1-4857-a7a6-1b39cb3ff4d2@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Gnoga Latest Updates From: David Botton Injection-Date: Tue, 14 Oct 2014 02:26:55 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 2246 X-Received-Body-CRC: 2478766549 Xref: news.eternal-september.org comp.lang.ada:22445 Date: 2014-10-13T19:26:55-07:00 List-Id: The issue was not the PO not being released in the AWS events. Was a poor a= nalysis of the issue by me mixing up two different variables.. I shouldn't = talk while debugging, I always eat the words in the middle when I do it : (= I just get excited in the hunt... I need less enthusiasm sometimes for th= ese things since humble pies haven't worked so far for me :) Ok, the fix is checked in to git. I changed how I handle holding the connection in the singleton so now works= as should. If Application.Singleton.End_Application is called or the browser window is= closed, Application.Singleton.Message_Loop will return. Any clean up can t= hen be made after that before the main procedure ends. David Botton