HDTenEightyP/NetNews huggingface dataset:
From: qualtrak@netcom.com (Qual Trak)
Subject: AddInput/WorkProcs questions
Followup-To: comp.windows.x.intrinsics
Reply-To: jb@QualTrak.COM
Organization: QualTrak Corporation
Distribution: usa
Date: Thu, 8 Oct 1992 14:42:11 GMT

I have an application that uses both XtAppAddInput () and
XtAppAddWorkProc () at different times to do its dirty deeds.  I've
noticed the following things.

    1.  When I use XtAppAddWorkProc () to add a work procedure, I find
        that other x events aren't necessarily handled until the work
        proc is finished.  Specifically, I pop up a window to say that
        what the program is doing will take a little time.  Sometimes
        the text that goes in the window isn't displayed fully until the
        work proc is finished.  I explicitly flushed the queue to the
        server - it just appears to me that the work proc is hogging the
        event queue.

    2.  In the same program I have to spawn a child process and attach a
        reader to him, which I do with XtAppAddInput ().  I then wait on
        the kid in a loop of the form

            while (ChildProcState (child) == ChildProcStateActive)
            {
                XtAppProcessEvent (app, XtIMAll);
            }
	    
	    I then do a final loop to get any residual output data from the
        child proc with

            while ((XtAppPending (app) & XtIMAlternateInput))
            {
                XtAppProcessEvent (app, XtIMAll);
            }

		I then use XtRemoveInput () to release the reader proc.  The
        problem I'm seeing is that the XtAppPending () &
        XtIMAlternateInput is allways returning True and the reader proc
        is called and reading 0 length records from the file he's
        supposed to be reading from.

	    By the time the program has dropped to theXtAppPending Loop, the
        child as terminated and closed his output files.  I'm confused
        about this one.

	Anybody got any thoughts about what I'm doing wrong?
------------------------------------------------------------------------
John Birchfield - QualTrak Corp (408) 730-2674 Home (408) 736-3852
jb@QualTrak.COM
------------------------------------------------------------------------
From: bobmcg@castle.ed.ac.uk (Bob McGonigle)
Newsgroups: comp.windows.x
Subject: Postscript to European X User Group Conference
Keywords: X, conference
Date: 7 Oct 92 16:55:21 GMT
Organization: Edinburgh University Computing Service

The recently held European X User Group conference and exhibition was
resounding success.  This is the fourth year the event has been held, and X
Windows continues to gain new ground and attract more players.

The exhibition was well-attended, with exhibitors offering a wide range of
X terminals, software development tools, training programmes and
connectivity products.  Exhibitors included NCD, Tektronics, V1, VisionWare
and IST.

Speakers addressed issues such as X for conferencing and group working;
current technological trends; X over slow lines; display PostScript and
graphics within X Windows.

Continuing the EXUG policy of inviting big names from the world of X, this
year three US-based experts headed the programme - Doug Young, Oliver Jones
and Bob Scheifler.  The programme included presentations by over 20
speakers, from eight countries.

Pre-conference tutorials proved a major attraction.  Subjects on offer this
year included 'Using C++ with Motif', Debugging X Programs', and a course
designed for newcomers to X - 'From Awareness to Understanding'.

The strength of interest shown in this year's conference has given a boost
to EXUG plans for 1993, including a rolling programme of tutorials,
seminars and workshops, to be held in centres in the UK and other EC
countries.

This year's proceedings are available for 30 pounds (inc.  P&P) from
EXUG, PO Box 458, Cambridge, CB3 8SD, Great Britain.  Payment by cheque
or credit card. 

For further information about the European X User Group and coming
events, telephone +44 (0)223 426534 or fax +44 (0) 223 420251.
From: bcs@cis.ufl.edu (Bradley C. Spatz)
Newsgroups: comp.windows.x
Subject: Getty login bypass with R5 xdm.
Date: 13 Oct 92 19:49:45 GMT
Article-I.D.: eng.1992Oct13.194945.4805
Reply-To: bcs@cis.ufl.edu (Bradley C. Spatz)
Organization: UF Computer Science Department

Hi.

Does anyone have a R5 xdm that allows a user to bypass the xdm
login - to login under getty?

We made modifications to the R4 xdm client to provide for such a hook,
so that Sunview users and such (who didn't want to start up a X
session) could press F2 and get a typical getty-login.

We are trying to duplicate the mods we made for R4 with R5, but
with no luck.  We seem to be mangling the environment.  Anyone
have experience with this?

Thanks in advance.
-- 
Bradley C. Spatz                                    Bytes:        bcs@ufl.edu
Computer & Information Sciences                     Bits:  uunet!uflorida!bcs
College of Engineering                              Waves:       904/392-1499
University of Florida           "School IS hell." -- Matt Groening
Newsgroups: comp.windows.x,comp.sys.dec
From: mjr@hussar.dco.dec.com (Marcus J. "Buddy can you spare a clue?" Ranum)
Subject: Re: X Under Windows NT
Organization: Digital Equipment Corporation, Washington ULTRIX Resource Center
Date: Wed, 7 Oct 1992 18:37:44 GMT

>This is that it appears that
>it will be difficult to run an X-server in "native mode" under WNT.

	Is this a bug or a feature?

	No, seriously - If you consider that X windows' installed
base is a drop in the bucket compared to ms-windows', Microsoft
would be crazy to put engineering effort into making X a priority.

>For a group like ours, which is actually looking favorably at WNT,
>these details are very disappointing. It appears that the X community
>will be ignored when Windows NT for Alpha comes out

	I think that a lot of the NT fans and potential NT fans out
there are expecting that the X community is going to dry up and blow
away. They may be right. Microsoft *did* sell a million copies of
windows last month, after all. X? (actually, in terms of installed
base, the X community dried up and blew away years ago)

	I don't know why you specify "Windows NT for Alpha", by the
way. NT is NT. The architecture it's running on will make some
difference, but presumably it'll behave the same and have the same
API across hardware. So if one NT has short-shrifted X, then they all
do.

mjr.
-- 
	It is important to focus on writing software that is "adequate."
Having one's software be "good" or even "excellent" is over-rated. If
"good" were necessary or even important, DOS would not be the de facto
standard operating system.                          -notebooks of a heretic
From: stroyan@hpfcso.FC.HP.COM (Mike Stroyan)
Date: Sat, 10 Oct 1992 19:28:21 GMT
Subject: Re: Help on XSetWindowColormap
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.windows.x

In comp.windows.x, mek@hydrox.enet.dec.com (Mark Klamerus) writes:

>         I'm writing an image display application.  This will be in Motif,
>         but the problem I'm running into is X (I think).  The gist of things
>         is problems with the colormaps.

The example is setting a different colormap for the drawing area widget than
for the other windows.  If you are using more than one colormap under a top
level window, you need to list the windows with unique colormaps in an
array of window id's in the WM_COLORMAP_WINDOWS property on the top level
window.  Consider that most X servers can only install one colormap at a time.
You can reorder the window list in the property to change the priority of
the colormaps.  This is effective if done in response to enter and leave
events for the windows with non-default colormaps.  Be certain to include
the top level window in the property list, or it will be implicitly placed
at the front of the list with the highest priority.

If you can get by with one colormap for all windows, then just change
the top level window to use your private colormap.  You will need to take
care to get all of the widgets drawn with good colors from the private
colormap instead of using indices appropriate to the default colormap.

Mike Stroyan, mike_stroyan@fc.hp.com
Newsgroups: comp.windows.x
From: perrier@divsun.unige.ch (Perrier Rene)
Subject: xpm3 pixmap editor wanted
Keywords: xpm
Organization: University of Geneva, Switzerland
Date: Wed, 7 Oct 1992 16:03:46 GMT

Hi Folks,

I'm looking for a program to edit some icons for my application.
These are kept as XPM version 3 pixmaps.

The only program I know of that edits XPM files is Xfedor, but
it only works with XPM version 2 pixmaps.

I looked in the FAQ and the only application other than xfedor mentioned
is olpixmap from ATT.  Any idea where I can find that?

Any pointers to other applications to do this would be appreciated.

#####################################################################
Rene Perrier                             e-mail: perrier@cih.hcuge.ch
Digital Imaging Group (U.I.N)
Computer Science Department (C.I.H)     ##   ##      ###       #   ##
University Hospital of Geneva            #   #       ##       # #  #
24, rue Micheli-du-Crest                ##  ##       #        # # #
CH-1211 Geneve 14                       #   #       ##       #  ##
Switzerland                            ##  ##      ##       #   ##
tel.: +41-22-3726268                   #####  ##  ###  ##  ##   #
fax : +41-22-3726198
#####################################################################
From: mjk@hoot.asd.sgi.com (Mark Kilgard)
Newsgroups: comp.windows.x
Subject: Re: General questions about X protocol and max sizes
Date: 13 Oct 92 01:31:01 GMT
Organization: Silicon Graphics, Inc.

In article <9210122016.AA03091@expo.lcs.mit.edu>, MCOG@CHVM1.VNET.IBM.COM ("Michael A. Coggins") writes:
|> (I sent the a while back, but I don't know if it got
|>  to the newsgroup.  Sorry if you are seeing this again.)
|> 
|> Question of possible interest for server gurus only:
|> 
|> Most of the dimensions for X and Y in the X protocol
|> are INT16 (signed int) and for width and height they
|> are CARD16 (unsigned int).
|> 
|> The X server sample does not really deal with these consistently
|> in all cases.  For example in miHandleExposures all x and y values
|> and width and height values are passed in as int, which is OK.
|> However, at one point there is the following code:
|> 
|> srcBox.x2 = srcx+width;     (x2 is a signed short)
|> 
|> The problem here is that if width is big (32768 to 65535) and srcx
|> is small (zero for example) then srcBox.x2 will be negative.
|> 
|> This can obviously cause problems down the road, particularly in
|> the case on which I am currently working.  How should this be
|> handled?  Should I attempt to find all these cases and report
|> them as "bugs"?  Should I chop down large widths whenever I
|> seem them in my ddx code?  (I'm only working in the ddx).
|> 
|> You might think normal clipping will handle this, but it doesn't
|> in this case for reasons too complex to describe in 200 words or less.

This is a problem discussed in a paper titled "Why X is
Not Our Ideal Window Sytem" by Hania Gajewsk, Mark Manasee,
and Joel McCormack, all of Digital Equipment.  The paper
can be found in the special X issue of _Software Practice and
Exeperience_ Vol20(S2) of October 1990.

The recommendation they make (to future X protocol revisers)
is "Width and height should be defined as either 15-bit unsigned
values, or better, as 16-bit signed integers with negative
values treated as errors.  In the C Xlib and XtK bindings, width
and height should be signed to match C arithmetic semantics.
In languages with subrange types, their type should be defined
as the range 0..32767.  The procotol should also explicitly
restrict all windows to be contained within the 16-bit signed
coordinate space of the root window."

My advice is since you probably don't have to have a window
that big, try to confine yourself to smaller windows.  2^15 is
pretty large.  This problem can probably be considered on
the "fringe" of X protocol conformance.  But the problem
is real.

I wonder if the X Test Suite tests conformance for large
windows.

- Mark
Newsgroups: comp.windows.x
From: mahan@TGV.COM (Patrick L. Mahan)
Subject: RE: X11R5 under VAX VMS
Organization: The Internet
Date: Mon, 12 Oct 1992 20:17:10 GMT

#
#This seems like an question that should be in the FAQ but it is not.
#
#Has anyone found success getting X11R5 to compile and run under any
#of the recent releases of VAX VMS?  How about VMS/Posix?  According to the
#RELNOTES.TXT file, the release should be able to be built on systems
#that are POSIX.1 compliant.  I haven't determined if the current DEC
#product, POSIX version 1.0, is truely POSIX.1 compliant although I would
#assume so.
#

Just having POSIX for VMS will not complete help out with building X11R5
under VMS.  In building the X11R5 distribution you face the following
problems:

	1) How to support both TCP/IP and DECwindows transport?

	   Digital did this by designing the "Common Transport" model,
	   that allows anyone to write a X windows transport for DECwindows.
	   Even if you don't use this model, and just go with TCP/IP then
	   you still have the added problem that TCP/IP is not fully
	   integrated VMS (for instance, doesn't support FD's).

	2) Missing "System" routines.

	   X Windows was primarily written under Unix.  This means that
	   it makes use of Unix system routines that may not be emulated
	   under VMS.

	3) Integration with existing DECwindows applications.

	   You might want ignore doing this, but at the cost of not having
	   the various DECwindows applications you already are use to having.

	4) At the present I know of no way to adequately build an X11R5 server
	   for VMS.  Digital at present doesnt' document the interface to its
	   graphics hardware vary well.

#
#From the lack of discussions about this, it must be either 1) so easy
#that everyone that has attempted it has not had any problems, 2) so
#hard that noone has even tried or 3) everyone running DECwindows/Motif
#is so happy that they don't even have to look at X11R5 (sorry, I just
#HAD to add that last one...;-).
#
1) It not so easy.  From my experience, the VMS users that read this newsgroup/
mailing list are few and far between.

2) I've tackled part of this problem (ported the X11R4 clients and demos to
VMS).  It took approx. 3 man months to finish (it ain't trivial).

3) I doubt everyone is happy with DECwindows/Motif (since it is X11R4 based).
It is very frustrating to wait for Digital to get X11R5 out the door.

As I understand it, Digital has three groups working on X Windows.  Xlib, Xt and
the client side of the transport is handled by the VMS engineering group.  The
server and server side of the transport is handled by the Workstation group.  
And Motif is handled by the Network Application Group.  So there are plenty of
people working on it.  Also, remember that Digital does try to maintain 
"quality assurance" and thus DECwindows/Motif is subject to this lifecycle as
well.

Patrick L. Mahan

--- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------

Waking a person unnecessarily should not be considered  - Lazarus Long
a capital crime.  For a first offense, that is            From the Notebooks of
							  Lazarus Long
Xref: sparky comp.windows.x:17565 comp.sys.dec:5346
From: forrest@nobozo.CS.Berkeley.EDU (Jon Forrest)
Newsgroups: comp.windows.x,comp.sys.dec
Subject: X Under Windows NT
Date: 7 Oct 1992 18:29:27 GMT
Organization: University of California, Berkeley
Distribution: world
NNTP-Posting-Host: nobozo.cs.berkeley.edu

The research group I'm in here at UC Berkeley is interested in running
Windows NT on DEC Alpha's. I've done some preliminary investigation
and I've found something that troubles me. This is that it appears that
it will be difficult to run an X-server in "native mode" under WNT.
(By "native mode" I mean an X-server that has complete control
of the display and that isn't running as some kind of subwindow under
Windows, which is the way the several current products work).

If you look at the block diagrams of WNT you see that there are a
number of "protected subsystems" that run on top of the WNT
Executive. Examples of these are the Win32 and POSIX subsystems.
The diagrams I've seen make it appear that these subsystems are
all equal. At first glance, I though it would be possible to run
an X-server (and Xlib) under the POSIX protected subsystem, or maybe
to even create a new protected subsystem that I'd call the X-server
protected subsystem.

It turns out that these assumptions are wrong, according to people
I've talked to at DEC. What appears to be true is that the Win32
subsystem is more equal than others and always controls the display
for all protected subsystems. Also, the POSIX subsystem does its I/O
through a tty emulator, which is under the control of the Win32 subsystem.
Furthermore, Microsoft hasn't released the API necessary to implement
a protected subsystem.

For a group like ours, which is actually looking favorably at WNT,
these details are very disappointing. It appears that the X community
will be ignored when Windows NT for Alpha comes out, assuming the
eXcursion product isn't acceptable (which may or may not be true).
People who tend to look for the negative may start accusing DEC of
another flip-flop since the X-based environment that DEC has been
promoting so heavily will be a second-class citizen under WNT.

I'd enjoy hearing people's comments about this, especially any corrections
to the way I've interpreted the facts.

-- 
Anything you read here is my opinion and in no way represents the Univ. of Cal.
Jon Forrest WB6EDM	 forrest@postgres.berkeley.edu	 510-643-6764
Newsgroups: comp.windows.x
From: raj@gdstech.grumman.com (Rajesh Chawla)
Subject: Looking for info on SIE
Organization: GRUMMAN DATA SYSTEMS
Date: Mon, 12 Oct 1992 13:59:54 GMT


Hi, 

I am looking for info on the imaging extension done by NCD, known as
SIE.  If anyone has any info or pointers to documentation, please let
me know.

Thanks,

-- 
==================================================================
Rajesh Chawla				2411 Dulles Corner Park
E-Mail:  raj@gdstech.grumman.com	Suite 500
Phone:	(703) 713-4170	FAX: 713-4103	Herndon VA 22071
Newsgroups: comp.windows.x
From: jimdu@comm.mot.com (Jim Duran)
Subject: Re: "paged" vs. panned virtual desktop
Organization: Motorola Land Mobile Products Sector
Date: Fri, 9 Oct 1992 21:34:13 GMT

In article <43882@ogicse.ogi.edu>, jbthiel@ogicse.ogi.edu (John B. Thiel) writes:
|> 
|> Is there a window manager or other mechanism to effect a virtual
|> desktop that is "paged" rather than panned? The idea is to have
|> a control w/ eg. 3x3 boxes that represent 9 subdivisions of the virtual
|> desktop. Clicking one of the boxes displays the corresponding part of
|> the desktop on the physical screen. The pages should be continuous (ie.
|> a window could be between pages), and ideally the 3x3 array would reflect
|> in miniature the sizes and positions of all objects on the desktop.
|> 
|> I have tried ctwm, but its pages are discrete, and the control consists
|> only of colored buttons.
|> 
|> Any pointers appreciated.
|> 
|> 
|> -- 
|> CSNET	jbthiel@cse.ogi.edu
|> UUCP    ...{sun,tektronix,verdix}!ogicse!jbthiel



Yes, I believe that a window manager I use quite extensively would help you.

It's called tvtwm . If you are familiar with Tom's Window Manager (twm) it
is simply an extension which adds the virtual desktop and icon management
features.  I find it quite useful.  Here's a portion of it's man page:

------------------------------------------------------------------------

tvtwm - Tom's Virtual Tab Window Manager for the X Window System

tvtwm [-display dpy] [-s] [-f initfile] [-v]

Tvtwm is a window manager for the X Window System based
on the X11R4 version of twm.  It includes a ``Virtual Desktop''
feature that effectively makes the root window of the screen 
larger than the physical limits of the display.  To change 
as little as possible in this manual, from here on the window
manager is referred to as twm.

Twm is a window manager for the X Window System.  It provides 
titlebars, shaped windows,
several forms of icon management, user-defined macro functions, 
click-to-type and pointer-driven keyboard focus, and user-specified 
key and pointer button bindings.

...

COPYRIGHT
Portions copyright 1988 Evans & Sutherland Computer Corporation; portions
copyright 1989 Hewlett-Packard Company and the Massachusetts Institute of
Technology,  See X(1) for a full statement of rights and permissions.

AUTHORS
Tom LaStrange, Solbourne Computer; Jim Fulton, MIT X Consortium;
Steve Pitschke, Stardent Computer; Keith Packard, MIT X Consortium;
Dave Payne, Apple Computer.

Virtual Desktop added by Tom LaStrange, Solbourne Computer.

------------------------------------------------------------------------

Hope this helps,
Jim D.


-- 
+------------------------------------------------+--------------------------+
| Jim Duran                                      | jimdu@ecs.comm.mot.com   |
| Control Centers Engineering - IL02 / Rm 1828   | CJD007@email             |
| Land Mobile Products Sector - Motorola Inc.    |--------------------------|
| 1301 E. Algonquin Rd, Schaumburg, IL 60196 USA | Voice: (708) 576-4297    |
+------------------------------------------------+--------------------------+
Newsgroups: comp.windows.x
From: engel@gdstech.grumman.com (Steve Engel)
Newsgroups: comp.windows.x
Subject: Ada Specifications for X11
Date: 9 Oct 92 20:31:30 GMT
Distribution: usa
Organization: Grumman Data Systems, Woodbury, New York, USA.

----------------------------------------------------------------------
This message is posted on behalf of John Whitson, not Steve Engel.
Please Reply to:  engel@gdstech.grumman.com, or by phone to John
at (516) 346-2892.
----------------------------------------------------------------------

	Hi!  As a newcomer to Ada and a previous C with X programmer,
	is there a documented standard interface for calling X routines
	from Ada? In particular:

	o	Is there an Ada Interface to Xlib?
	o	Is there an Ada Interface to Xt?
	o	Are there any Widget sets like Athena, Motif, etc. that
		were ported to Ada?
	o	Are there any native Ada Widget sets?

	Please send any repies / helpful information to this address:
	engel@gdstech.grumman.com.  Thanks!!

	John Whitson
Newsgroups: comp.windows.x
From: rchui@nswc-wo.nswc.navy.mil (Raymond Chui)
Subject: Is Legal to Create GC Without XCreateGC?
Organization: Naval Surface Warfare Center - White Oak
Date: Tue, 13 Oct 1992 20:05:39 GMT

Since there is no comp.window.x.xlib newsgroup. This is the group
for my question.

Is Legal to Create GC Without XCreateGC?
For example:

main()
GC gc_1, gc_2;
XValues gcv;
....
....
gcv.xxx = xxxxxx;
gc_1 = XCreateGC(XtDisplay(widget),
		RootWindowOfScreen(XtScreen(widget)), 
		GCXxxx | GCXxxx, &gcv);
/* Now create gc_2 without use XCreateGC() */

gcv.xxx = new_xxxx;
gc_2 = XChangeGC(XtDisplay(widget), gc_1, GCXxxx | GCXxxx, &gcv);
/* OR */
XCopy(XtDisplay(widget), gc_1, GCXxxx | GCXxxx, gc_2);

If the above statements are illegal. Please someone tell why? and 
what I shall do?

Thank you advance!


-- 
Raymond H. Chui
NSWC N62
10901 New Hampshire Ave.
Silver Spring, MD 20903-5000
U.S.A.
Voice:1-301-394-5192 Fax:1-301-394-5835
E-Mail:rchui@nswc-wo.nswc.navy.mil
 _ __                                  _    ,    __
' )  )                           /    ' )  /    /  ) /
 /--' __. , , ____   ______   __/      /--/    /    /_  . . o
/  \_(_(_(_/_/) ) )_(_) /) )_(_(_     /  ( o  (__/ / /_(_/_(_
          /
         '
Newsgroups: comp.windows.x