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.182.104.69 with SMTP id gc5mr13034047obb.18.1413809768469; Mon, 20 Oct 2014 05:56:08 -0700 (PDT) X-Received: by 10.140.39.85 with SMTP id u79mr2743qgu.16.1413809768439; Mon, 20 Oct 2014 05:56:08 -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!news.glorb.com!uq10no14230390igb.0!news-out.google.com!i10ni96qaf.0!nntp.google.com!dc16no4137871qab.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 20 Oct 2014 05:56:08 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=108.44.225.195; posting-account=vk6_JwoAAABkMyHO1YfdP69Hm3CpbdGR NNTP-Posting-Host: 108.44.225.195 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Launching Popup Windows in Gnoga From: Jeremiah Injection-Date: Mon, 20 Oct 2014 12:56:08 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:22608 Date: 2014-10-20T05:56:08-07:00 List-Id: I've been slowly working through the tutorials as I have time. More recent= ly I have been playing with the material from the Popup window. Spending s= ome more time of my own with it in my own programs has brought up some ques= tions. Keep in mind, I am initially working in a Singleton environment (my= needs lie there for my first project coming up). I do plan on multi_conne= ct later as well, but I want to focus on learning the environment under Sin= gleton, since that applies more to what I need to do at this time. 1. In the tutorial (I think it is Tutorial 6), the program calls Launch to= launch the window and the delays some time to allow it to come up before a= dding elements to it (views, buttons, etc.). This seems ok at first but wh= en I try it on various windows boxes, sometimes the delays are too short an= d sometimes they are fine. I could always increase the delay time, but fro= m a user perspective this could be annoying and I can never really control = how long it takes to spawn a window. If I miss the timing, the window come= s up blank (elements aren't added??). Is there a better way to catch when = it is ok to add elements to the window so they appear? I am guessing an ev= ent, but the couple I have tried so far didn't quite do it yet. The delay = method, while quick and effective for a tutorial, isn't quite solid enough = for a desktop application that I am planning. 2. Is there a way to relaunch a window? If I call Launch more than once, = I get an error indicating the item is already created. I don't need to rec= reate the window, but simply show it again. This would be helpful if I wan= t to maintain a data state associated to the window. Currently, once the e= vent that spawned my window is over, I lose all state. I can work around t= his by passing in objects, but I was wanting to see if the window was relau= nchable / reshowable so I could easily control when/how its GUI elements we= re destroyed. 3. This is related to #2, but is there a way to create elements well enoug= h so I can do things like attach other elements or callbacks to them but se= parately control when they show on the screen? This is more a "trying" to = understand how it works thing, but also with some of the timing considerati= ons mentioned above, being able to control when I "setup" an element vs. wh= en I view it would be very nice (at least in windows where I have to deal w= ith various OS / Program delays that I cannot control. This is more for the author if he sees this, but anyone can comment: 4. Will there eventually be some more documentation on what each method an= d parameter are for? I don't mind exploring/playing and I understand Gnoga= isn't even officially released, but I know in the future, being better abl= e to understand how each component works would be useful. I am assuming I = have more trouble because I don't do web development, so the concepts are e= ither foreign to me or different from what I am used to in a normal windows= GUI environment.