[comp.windows.x] x

RWS@ZERMATT.LCS.MIT.EDU.UUCP (02/12/87)

    Also, is there going to be a [protocol] document with an index. It would
    make it a lot easier to read when one hasn't quite gotten down the
    myriad of definitions ...

If you get the latest /pub/x11.spec* files on zap.mit.edu, you will find
an unpaginated document, a paginated document, a table of contents, an
index (of sorts) for the paginated document, and a shell script to
regenerate them if you want a different page size.  You will also find
a file listing the revisions from this Alpha Test version of the
document and the Nearly Release version.

rich@oxtrap.UUCP (K. Richard Magill) (10/17/87)

What's this stuff about a "typical /etc/ttys line" in X(8c)?

A typical line in /etc/ttys might be:

  ttyv0 "/etc/xterm -L =-1+1 :0" xterm on secure window="/etc/Xvs100 0 -c -l"

No unix system I've seen yet had an /etc/ttys like that!  Is this a
local hack?  Ultrix?  Undocumented BSD?  (From the Xvs100, my guess is
Ultrix)

xoxorich.
----------
Prolonged input from wiped tape can produce hypnagogic hallucination.

mkhaw@teknowledge-vaxc.ARPA (Mike Khaw) (10/17/87)

in article <1725@oxtrap.UUCP>, rich@oxtrap.UUCP (K. Richard Magill) says:
>   ttyv0 "/etc/xterm -L =-1+1 :0" xterm on secure window="/etc/Xvs100 0 -c -l"
...
> No unix system I've seen yet had an /etc/ttys like that!  Is this a
> local hack?  Ultrix?  Undocumented BSD?  (From the Xvs100, my guess is

Ultrix uses this format.  I got the impression from the Ultrix documentation
that this was in 4.3bsd, based on the discussion of "secure" ttys (i.e., ttys
on which the system will allow root to login), but I could well be mistaken.

Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303

guy%gorodish@Sun.COM (Guy Harris) (10/17/87)

> No unix system I've seen yet had an /etc/ttys like that!  Is this a
> local hack?  Ultrix?  Undocumented BSD?  (From the Xvs100, my guess is
> Ultrix)

Nope.  Try *DOCUMENTED* 4.3BSD.
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com

dce@mips.UUCP (David Elliott) (10/20/87)

In article <1725@oxtrap.UUCP> rich@oxtrap.UUCP (K. Richard Magill) writes:
>What's this stuff about a "typical /etc/ttys line" in X(8c)?
>
>A typical line in /etc/ttys might be:
>
>  ttyv0 "/etc/xterm -L =-1+1 :0" xterm on secure window="/etc/Xvs100 0 -c -l"
>
>No unix system I've seen yet had an /etc/ttys like that!  Is this a
>local hack?  Ultrix?  Undocumented BSD?  (From the Xvs100, my guess is
>Ultrix)

This is documented 4.3BSD and later versions of Ultrix.

-- 
David Elliott		dce@mips.com  or  {ames,decwrl,prls}!mips!dce

brucek@hpsrla.HP.COM (Bruce Kleinman) (05/21/88)

From the book of X (HP's Programming With the X Windows System) ...

    " XSelectInput defines which input events the window is interested in.
      If a window is not interested in an event, it usually will propagate
      up to the closest ancestor that is interested. "

It will *usually* propagate up?  I am looking for a more definite definition.

I would like to create a window with no input event handling of its own.
Specifically, I would like input events to map through to the root window.
What I need is the 'inverse' of a transparent window - a window that obscures
other windows for the purposes of *output* only.  Any ideas?

BTW, before anyone points out how easy this is in X11: I am using X10.


                              Bruce Kleinman
           brucek%hpnmd@ce.hp.com  -or-  ....hplabs!hpnmd!brucek

price@WSL.DEC.COM (05/22/88)

> What I need is the 'inverse' of a transparent window - a window that obscures
> other windows for the purposes of *output* only.  Any ideas?

Sure would be nice, but it doesn't exist, either in X10 or X11. It would be *really*
nice if one could restrict input to a region, but I'm sure Bob S. and Jim G. would
have aged much more than they have already if they tried to design that
in for us. (At least Jim seems to be recovering nicely from his experience...).
If we had input clipping to a region, I believe we would have what Bill Joy
has been crying for: relief from the "curse" of the rectanglular window.
(Shudder shudder). It's my understanding that we would pay for this hack
with poorer performance overall.

-chuck

scott@grlab.UUCP (Scott Blachowicz) (05/11/89)

Hi-
  We're having problems running our X11 application that was compiled and
loaded on an HP 9000/825 (HP-UX v3.01) system. When running it on an
HP9000/370 (HP-UX v6.5) X server, our Starbase-on-X program gets a bus
error. This same program works fine when run on our HP9000/320
(HP-UX v6.2) X server. I have a small test program of mine that just makes the
Starbase graphics routine calls to open the "display" (i.e. a window
created with the xwcreate(1) command) with the "sox11" display driver,
then draws an "X", closes the "display" and exits. This program works
fine on the HP-UX v6.5 system. Anybody got any ideas as to what could
cause the same program to work when running with one display server and
not with another.

Specifics summary:
  -Machines (& what /usr/bin/X11/X /usr/lib/libX11.a command)
     HP9000/825 HP-UX v3.01
         /usr/bin/X11/X:
            X11 (A.B3.00.6B)
            ...
            200.1.3.1   08/12/88 libdd98720w.a
            200.1.3.1   08/12/88 libdd98720.a
            200.1.3.1   08/12/88 libdd98730.a
            200.1.3.1   08/12/88 libsb1.a
            200.1.3.1   08/12/88 libsb2.a
         /usr/lib/libX11.a:
            Context.c   1.5   2/24/87
     HP9000/320 HP-UX v6.2
         /usr/bin/X11/X:
            X11 (A.00.00)                              
            ...
         /usr/lib/libX11.a:
            Context.c   1.5   2/24/87
     HP9000/370,340 HP-UX v6.5
         /usr/bin/X11/X:
            X Window System, Version 11    HP-UX 6.5    A.01    $Revision: 9.1 $
            250.1.2.1   01/27/89 libxd300h.a
            250.1.2.1   01/27/89 libxd300l.a
            250.1.2.1   02/01/89 libxd98550.a
            250.1.2.1   01/27/89 libxd98720.a
            250.1.2.1   01/27/89 libxd98730.a
            250.1.2.1   01/27/89 libsdiutils.a
         /usr/lib/libX11.a:
            X Window System, Version 11    HP-UX 6.5    A.01    $Revision: 1.1 $

  -All of our code is compiled/loaded on the HP9000/825(HP-UX v3.01)
   system.

  -Only the small test program (gopen,dcmove,dcdraw,...,gclose) works on
   the 6.5 X server.

Now to recompile everything with debug...

Thanx for any help!
Scott Blachowicz
USPS:  Graphicus                UUCP:    ...!hpubvwa!grlab!scott
       150 Lake Str S, #206     VoicePh: 206/828-4691
       Kirkland, WA 98033       FAX:     206/828-4236

dvu%prism@GATECH.EDU (10/05/89)

Would you point me to the X (toolkits, Xlib, etc) documentation.  Thanks


Dinh Vu (dvu@prism.gatech.edu)

dvu%prism@GATECH.EDU (10/05/89)

Would you point me to the X (toolkits, Xlib, etc) documentation.  Thanks.

Dinh (dvu@prism.gatech.edu)

hemant@qcav01.enet.DEC.COM (12/29/90)

Hello

Greetings from India and best wishes for 1991.

We are from System Engineering Group of Digital (India) - an affiliate of DEC.
We are trying to use PC workstations as X-terminals under DECwindows.
Would it be possible to obtain X Version 11 Technical/programmer's details
in order to do a feasibility study?

Got this reference from VAXnotes conference on X.

thanks in advance.
regards
hemant

green@picker.picker.com (tim green) (04/30/91)

testing, thank you very much