Xref: utzoo comp.windows.x:15710 comp.databases:4376
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!usc!apple!fox!portal!cup.portal.com!truett
From: truett@cup.portal.com (Truett Lee Smith)
Newsgroups: comp.windows.x,comp.databases
Subject: Re: X and UNIFY Embedded SQL
Message-ID: <24787@cup.portal.com>
Date: 7 Dec 89 07:38:21 GMT
References: <637@ncis.tis.llnl.gov>
Organization: The Portal System (TM)
Lines: 20

Since I may have been the person who brought this up, let me comment on what
I found out.

It turns out that Unify has a problem with windowing environments only when
you use one of their programs that interacts with the keyboard.  The HLI
library does not have a problem since it does not change any signal handlers
once it has finished initializing itself.  Thus, properly constructed code
for handling the selectors and interactors in X and InterViews work just fine
if only the HLI functions are being used.

I found this out once I got the right engineer in my own organization talking
to the Unify support person.  By the way, I have had very good experience 
with Unify support.  Their support system gives me the same feeling of confi-
dence that the Oracle support system did when I dealt with them in the past.
Of course, in both cases I was a developer, not an end user.

Truett Smith
NEC America

(I don't speak for NEC, I'm not fluent in Japanese anyway.)