Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!hplabs!hp-pcd!hpcvlo!fred
From: fred@hpcvlo.HP.COM (Fred Taft)
Newsgroups: comp.windows.x
Subject: Re: XrTextEditor some problem
Message-ID: <3940011@hpcvlo.HP.COM>
Date: Thu, 7-May-87 18:27:44 EDT
Article-I.D.: hpcvlo.3940011
Posted: Thu May  7 18:27:44 1987
Date-Received: Sat, 9-May-87 19:02:06 EDT
References: <5200001@uicsrd>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 27


Without additional information, it's difficult to determine why you are
having problems with the text editor.  XrInput() most likely has nothing
to do with the problem; it does, however, do an XFlush(), which would
explain why the X error was appearing at that point.  When an application
makes an Xlib call, the request is not necessarily sent to the server
immediately; it is queued up until either the buffer fills, or the buffer
is flushed.  Needless to say, any call you are making before the call
to XrInput() could be the culprit.

A simple way to determine if the text editor is the problem would be to
place an XFlush() call right before and right after your call which
creates the text editor instance.

Also, have you remembered to do an XrInit() call before creating the
editor?  Did you register the window, using XrInput (MSG_ADDWINDOW)?
If so, did you remember to fill in the xrWindowData structure with the
proper foreground and background tiles?

If the problem still persists, extract the portion of your code which
creates the text editor instance (along with the section showing the
'info' structure for the editor), and post it as a response here;  I'll
look at it at the next available chance.

Fred Taft
Corvallis Workstation Operation
Hewlett-Packard Co