Re: Properties

[Maciej Sobczak <see.my.homepage@gmail.com>]

On Dec 1, 7:22 pm, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
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