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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c4ce0116ed6e67d5 X-Google-Attributes: gid103376,public From: "Jeff Creem" Subject: Re: X Motif in Gnat Ada Application Date: 2000/05/02 Message-ID: <8enqid$rrs$1@pyrite.mv.net>#1/1 X-Deja-AN: 618488735 References: <8enj57$2e8$1@nnrp1.deja.com> <390F691F.4E0473BA@raytheon.com> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Complaints-To: abuse@mv.com X-Trace: pyrite.mv.net 957312397 28540 199.125.98.22 (3 May 2000 00:06:37 GMT) Organization: MV Communications, Inc. X-MSMail-Priority: Normal NNTP-Posting-Date: 3 May 2000 00:06:37 GMT Newsgroups: comp.lang.ada Date: 2000-05-03T00:06:37+00:00 List-Id: Stanley R. Allen wrote in message news:390F691F.4E0473BA@raytheon.com... > Ted Dennison wrote: > > > > I don't know if its any better today, but back in the paleozoic era when > > I was doing Motif work, it was definitely *not* thread/task safe. If you > > wanted to use Motif with multitasking programs, you had to be sure that > > only one task actually made all the X/Motif calls; sort of a Motif server. > > > > My understanding is that "thread safety" was the major feature > which distinguished X11R6 -- the final revision of X. > > -- > Stanley Allen > mailto:Stanley_R_Allen-NR@raytheon.com It is true that X CAN be built so that it is thread safe, however Motif is still not thread safe. This does not mean that you can not use tasks but you need to make sure only one task ever directly interacts with the GUI...I bit of a pain...