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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,36a29c2860aff686 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!fl7g2000vbb.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: Properties Date: Wed, 1 Dec 2010 13:35:32 -0800 (PST) Organization: http://groups.google.com Message-ID: References: <3b84c8e7-1a51-4a7c-9646-119f1fc51478@s4g2000yql.googlegroups.com> <4pnv7nl4cdui$.1n28i7lqk4mek$.dlg@40tude.net> <1k7367gtebsgm$.18auo6u3nfg34.dlg@40tude.net> <1u5dftkqqi68c.10079qnqyyfwb$.dlg@40tude.net> NNTP-Posting-Host: 83.77.92.213 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1291239332 25605 127.0.0.1 (1 Dec 2010 21:35:32 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 1 Dec 2010 21:35:32 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: fl7g2000vbb.googlegroups.com; posting-host=83.77.92.213; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Xref: g2news1.google.com comp.lang.ada:15735 Date: 2010-12-01T13:35:32-08:00 List-Id: On Dec 1, 7:22=A0pm, "Dmitry A. Kazakov" wrote: > > Perhaps the scope you have in mind is too large. Is it really > > necessary to have the GUI operate outside of one task? > > Affirmative. Consider an oscilloscope widget indicating real-time data. > Consider a debug window showing log messages from different tasks. And how is this any different from, say, printing exactly the same log messages on standard output? You do not expect different tasks to spit their stuff directly to Ada.Text_IO and have it working properly, right? How do you solve this problem with Ada.Text_IO? Why the same solution cannot apply to GUI? I don't see any problem with single-threaded GUI, as long as there are ways to communicate with it. It is the communication part that has to be task-safe, not the GUI as a whole. > > Leave the task handling to the application designer. > > Obtrusive and inefficient. I did it for GtkAda. It is quite uncomfortable > to use, and if you forget to route GTK requests to the main task, you get > sporadic crashes difficult to trace down, quite nasty. I thought that Ada has enough tools to support arbitrary visibility and access strategies. If you can "forget to route GTK requests to the main task", then there is some package/typing problem in the code. Is GUI to be blamed for this? -- Maciej Sobczak * http://www.inspirel.com