HDTenEightyP/NetNews huggingface dataset:
From: curts@tmpcu.mdc.com (Curt Schroeder)
Newsgroups: fj.mail-lists.x-window
Subject: Re: X: User simplicity vs code complexity
Date: 29 Jul 92 17:00:58 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: Wed, 29 Jul 92 08:59:22 -0500
Message-Id: <9207291359.AA26351@tmpcu.mdc.com>


[original quote about complexity deleted]

> If you compare the Xlib and IRIS GL on Silicon Graphics you see that
> many things can be done a lot easier.
>
> IRIS GL heavily relies on defaults and most of the function calls
> only specify what has not been specified before.
>
> The following opens two windows and draws two different triangles in them:
> If you compare Xlib : -------------------------------
[part of the code segement deleted]
        points[0].x = 0;                points[0].y = height-1;   /* Redraw */
        points[1].x = (width-1)/2;      points[1].y = 0;
        points[2].x = width-1;          points[2].y = height-1;
        XDrawLines(dpy, win1, gc, points, 3, CoordModeOrigin);
> ... with IRIS GL  : -------------------------------
        winset(win1);                   /* Redraw */
        bgnclosedline();
        v2i(0, 0);
        v2i((width-1)/2, height-1);
        v2i(width-1, 0);
        endclosedline();
> ... you see that IRIS GL is concise and Xlib is not.

I would like to temper this with the statement that it depends on what you are
doing.  In this short example, GL does look more concise.  However, consider
an aplication where you have many polylines to draw, of varying numbers of
segments within the polyline.  With X, all I have to do is pass each array of
polyline segments to XDrawLines.  With the above example GL code, I would need
to write a procedure of my own, just to give me the same functionality that
comes with X.

I think the biggest difference here is that GL is optimized for Silicon 
Graphics dedicated graphics hardware, but X is intended to be installed on
many different systems.  This is _almost_ comparing apples and oranges, I 
think.  I confess that I have very little experience with GL.  My opinions
here are largely based on Rainer Sinkwitz's example.  I understand that GL is
very good at doing some types of applications, because of its specialized
nature.  X is more platform generic (IMO), at hence may appear to have more
complexity for certain operations than other graphics libraries.

Note: the X code could be improved in the original example by only changing
the points[].y values to draw the second triangle.

Curt

Curt Schroeder | McDonnell Douglas Missile Systems Company      |
----------------------------------------------------------------|
These opinions are mine, mine, mine!  I  | curts@tmpcu.mdc.com  |
am not an instantiation of Std_Employee! | - Apple II Forever - |
From: klute@tommy.informatik.uni-dortmund.de (Rainer Klute)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Touchscreens and Multple Pointer Devices
Date: 24 Jul 92 11:22:32 GMT
Distribution: fj
Organization: University of Dortmund, Germany

Date: 24 Jul 92 05:06:52 GMT
Message-Id: <14o35dINN3er@fbi-news.Informatik.Uni-Dortmund.DE>
Newsgroups: comp.windows.x

In article <1992Jul23.210636.26915@crd.ge.com>, doel@ausable.crd.ge.com
(Michael Doel) writes:
|> In article <5720@taurus.cs.nps.navy.mil>, hebo@hp850.mbari.org (Bob
|> Herlien) writes:
|> > I want to add a touchscreen to some X terminals for a control/display
|> app
|> > I'm developing, and I have some general questions about how they're
|> integrated
|> > into an X environment.
|> 
|> [...]
|> 
|> Not having spoke to your vendor, I can only assume that you were a bit
|> misled.  As I understand it, X11Rn (for all n) will only allow one
|> pointing
|> device.  To allow more than one would require a relatively large change
|> to the X protocol (hence X12R1 ?).  In particular, the event structure
|> would
|> need to include a field to indicate which pointing device generated the
|> event.  You can't just add this to X11R5 and still have X11R4 apps
|> working
|> correctly.

You might wish to take a look into the X Input Extension coming with the
X11R5 source distribution. Here some quotes from the documentation, which
you will find in mit/doc/extensions/xinput:

    The design approach of the extension is to define  functions
    and  events analogous to the core functions and events. This
    allows extension input devices and events to be individually
    distinguishable from each other and from the core input dev-
    ices and events .  These functions and events make use of  a
    device identifier and support the reporting of n-dimensional
    motion data as well as other  data  that  is  not  currently
    reportable via the core input events.
    
    ...
    
    The input extension controls access to input  devices  other
    than  the  X  keyboard and X pointer.  It allows client pro-
    grams to select input from these devices independently  from
    each  other  and independently from the core devices.  Input
    events from these devices  are  of  extension  types  (Devi-
    ceKeyPress,  DeviceKeyRelease, DeviceButtonPress, DeviceBut-
    tonRelease, DeviceMotionNotify, etc.) and contain  a  device
    identifier  so that events of the same type coming from dif-
    ferent input devices can be distinguished.
    
    ...
    
    This extension is designed to accommodate new types of input
    devices  that  may  be  added  in  the future.  The protocol
    requests that refer to  specific  characteristics  of  input
    devices  organize  that information by input device classes.
    Server implementors may add new  classes  of  input  devices
    without changing the protocol requests.

I hope this helps.

-- 
  Dipl.-Inform. Rainer Klute      klute@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB
  Postfach 500500         |)|/    Tel.: +49 231 755-4663
D-W4600 Dortmund 50       |\|\    Fax : +49 231 755-2386
From: wiltzius@anduin.ocf.llnl.gov (Dave Wiltzius)
Newsgroups: fj.mail-lists.x-window
Subject: Xt/Motif and Visuals
Date: 28 Jul 92 04:39:50 GMT
Distribution: fj
Organization: Lawrence Livermore Nat'l Lab.

Date: 27 Jul 92 22:51:48 GMT
Message-Id: <131608@lll-winken.LLNL.GOV>
Newsgroups: comp.windows.x


Using the X-toolkit or Motif, is there a way I can create a
widget and window and specify the visual being used?  This seem
trivial with X since the visual is an argument to the XCreateWindow
call, but I'm hunting for the incantation for Xt and Motif and,
obviously, have not found it yet.  Any help would be greatly
appreciated.

Please respond via email.  And many thanks.
  Dave Wiltzius
  Lawrence Livermore Nat'l Lab
  wiltzius@llnl.gov
From: elder@enuxha.eas.asu.edu (Greg Elder)
Newsgroups: fj.mail-lists.x-window
Subject: Still Have Problem on Sun
Date: 22 Jul 92 05:59:17 GMT
Distribution: fj
Organization: Arizona State University

Date: Tue, 21 Jul 1992 18:42:11 GMT
Message-Id: <1992Jul21.184211.10537@ennews.eas.asu.edu>
Newsgroups: comp.windows.x

I'm still having problems getting an X program to link on a Sun workstation.
Again, this is a program which links and runs fine on a DEC ULTRIX
workstation, which I would like to have run on a Sun as well.  Below is
the command line I use to link everything, with the resulting error
message:

cc -o map -O -I/usr/openwin/include -L/usr/openwin/lib map.o initapp.o
xwinutil.o xbutton.o -lXm -lX11 -lXt

ld:  undefined symbol
        __XtInherit
        _XtToolkitInitialize

I haven't been able to figure out why this error pops up.  Aren't these
two routines in libXt.a?  I'm new to using Suns, so please let me know if
I'm missing something that is obvious.  Any help is appreciated.  Thanks.


--
  Greg Elder               | "Artificial intelligence?!!!  I'd rather
  Dept of Computer Science | have real intelligence." 
  Arizona State University |                      -- Ann Elder
  elder@enuxha.eas.asu.edu |
From: generous@sti.nasa.gov (Curtis Generous)
Newsgroups: fj.mail-lists.x-window
Subject: X Font problem in x3270
Date: 26 Jul 92 01:41:21 GMT
Distribution: fj
Organization: Goddard Space Flight Center

Date: Sat, 25 Jul 1992 12:46:30 GMT
Message-Id: <generous.712068390@nova>
Newsgroups: comp.windows.x


I am getting the error: 'Warning: Cannot convert string "3270" to type FontStruct' when
running x3270.  No characters appear on the window.  The procedure used to install the
3270 font was (taken from the Makefile):

	    bdftosnf -t 3270.bdf >3270.snf
	    for i in 3270.snf; do\
		    (set -x; install -c  $i /usr/lib/X11/fonts/misc);;\
	    done
	    mkfontdir /usr/lib/X11/fonts/misc

The fonts.dir file was properly updated, and all permissions look okay.  Any ideas?

--curtis
--
Curtis C. Generous
NASA STI
generous@nova.sti.nasa.gov
From: franklin@ug.cs.dal.ca (Steve "edified" Franklin)
Newsgroups: fj.mail-lists.x-window
Subject: I NEED HELP PLEASE
Date: 28 Jul 92 19:12:39 GMT
Distribution: fj
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada

Date: Tue, 28 Jul 1992 14:28:43 GMT
Message-Id: <Bs3s7v.AFH@cs.dal.ca>
Newsgroups: comp.windows.x

I hope to God this isn't the wrong forum, but I was hoping someone could
give me some advice... I am stricken with the plight of full time summer
school ( 5 courses!) and they leave me with lots of time at the
university. To fill in this time, I have recently been fiddling with
the x-windows systems. However, there are two problems:

1) there isn't much to play with
2) I try compiling my own stuff with imake and make, but the damn software
   insists that it needs some widget class library?

I got alot of software from gatekeeper.net.com /pub/X11/contrib,
but it seems that most of the stuff requires some widgetclass stuff.
Not being much of an x-windows master, I am only adept enough to be
able to modify the imakefile. Beyond that, I am hopeless...

My question is: Are there any good programs or games available out
there that might keep me busy? I have seen xtrek, and it is quite good.
Unfortunately, it's not quite so fun to play on your own and I've already
gotten pretty bored with it. Any other ideas or suggestions? I'd appreciate
all and any you might have.

thanks in advance muchly,

steve
-- 
aasdSteveFranklin-Subliminal Psychology Major.ks;dlasBlueJaysRULEkasdfeahsdbfl
sd;lfaswoq[eBuyMeAQuadra!!!mbnZMXCNdfsba;KdSPAMiuroqiyetIBMSuxiweuryth'ewr;mxn
qpuepriuPartyOneqtuj;,n.,xnc,kjasFlameMeNot!;lkj;lkgkjd;askElvisLivesjhfquweru
zx.cfranklin@ug.cs.dal.ca,sk;t;lrut[Superboy@ac.dal.cav.zx,Physics!eq3rwkh;oHA
From: gordie@duts.ccc.amdahl.com (Gordon Freedman)
Newsgroups: fj.mail-lists.x-window
Subject: Question: How can child of fork do XtAppAddInput?
Date: 30 Jul 92 09:23:13 GMT
Distribution: fj
Organization: Happy hacker bait and tackle shop

Date: 29 Jul 92 23:18:48 GMT
Message-Id: <edOo02zi1bar01@JUTS.ccc.amdahl.com>
Newsgroups: comp.windows.x

I have an application that forks a child process. What I want to do is close the
parent X Connection in the child proc, than get the child process set up so that
it can do XtAppAddInput (socket), and let XtAppMainLoop() handle events.

I keep getting an error EBADF from the select called (eventually) from XtMainLoop,
I'm guessing this is for the parent's X connection I closed, which the intrinsics
are still using for the select.

Here's (roughly) an example of what I am trying to do:
----------------------

void
SomeClass::memberFunc ()
{
	// XCon, XDisplay, and XApp are static member data in SomeClass
	// _id and _socket are member data for this instance of SomeClass

	// does a fork (), if parent or error returns pid
	// If child, continues on ...

	pid_t pid = ::fork () ;
	
	if (pid != 0)
	{
		// If parent also does ::XtRemoveInput and ::close for _socket
		// since only child is using it ...
		return pid ;
	}
	
	if (XCon >= 0)
	{
		// Close parent's X Connection
		::XtCloseDisplay (XDisplay) ;
		XCon = -1 ;
	}
	// Create an appcontext so we can use XtAppMainLoop/etc.
	XApp = ::XtCreateApplicationContext () ;

	// Add our socket to input list
	_id = ::XtAppAddInput (XApp, _socket, 
			(void*) XtInputReadMask, XSignal, (void*) this) ;

}

void
StaticMemberCallback (XtPointer client)
{
	SomeClass* p = (SomeClass) client ;
	p -> memberFunc () ;
}

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

StaticMemberCallback is invoked out of XtMainLoop, calls MemberFunc, and after
StaticMemberFunc returns to MainLoop I get the same message repeatedly:

Warning: Select failed; error code 9

This is from the child process, as I stopped the parent with a breakpoint.

Thanks in advance for any help.

Gordon Freedman
gjf00@duts.ccc.amdahl.com
Sigs are for kids
From: p00051@mail.psi.net (Marshall Caro)
Newsgroups: fj.mail-lists.x-window
Subject: Spy Program
Date: 28 Jul 92 05:53:24 GMT
Distribution: fj
Organization: PI Systems

Date: 27 Jul 92 19:08:01 GMT
Message-Id: <712274796.2.p00051@mail.psi.net>
Newsgroups: comp.windows.x

Does anyone know of a SPY program that will capture X Protocol messages 
to and from the X Server???

				Thanks,
				James Talvy
From: hebo@hp850.mbari.org (Bob Herlien)
Newsgroups: fj.mail-lists.x-window
Subject: Touchscreens and Multple Pointer Devices
Date: 24 Jul 92 09:00:52 GMT
Distribution: fj
Organization: Monterey Bay Aquarium Research Institute

Date: 23 Jul 92 17:40:09 GMT
Message-Id: <5720@taurus.cs.nps.navy.mil>
Newsgroups: comp.windows.x,comp.sys.hp

I want to add a touchscreen to some X terminals for a control/display app
I'm developing, and I have some general questions about how they're integrated
into an X environment.

Environment: HP 700RX X-terminals on an HP 9000/750 workstation.
             HP-UX 8.07, X11R4, Motif 1.1(.?)

Application:  Display & control of an ROV (Remotely Operated Vehicle), 
    basically a robot submarine.  Four copies of the app may be running 
    (ROV pilot, co-pilot, chief scientist, assistant scientist).

Ideally, I'd like to be able to have the pointing device configurable
between the touchscreen and a trackball (mice don't work on a rolling ship).
The pilot, who is normally preoccupied, needs to be able to "hit" a control
quickly, hence the touchscreen.  However, he may want to ask the co-pilot to
do some more detailed input which requires either a trackball or keyboard.
I'd like to keep all 4 stations identical in hardware, using software for
configuration.

The touchscreen vendor I've located stated that X11R4 uses only a single
pointing device, but that X11R5 can have multiple ones.  How does this work?
Are there multiple mouseforms on the screen?  Are they both generating
events?  In Motif (1.2, I assume), can events from either device trigger
callbacks (arm, activate, etc)?

Also, since I don't have R5 yet, can the pointer device be easily switched
in R4?  Where/how does one do this?  Does anybody know when HP will release
R5/Motif 1.2?

Finally, since a touchscreen doesn't have buttons, how does one distinguish
between motion and button events using a touchscreen?

Thanks for any information you can give me.

--------------------------------------------------------------
Bob Herlien
MBARI (Monterey Bay Aquarium Research Institute)
hebo@mbari.org
"Limit congressmen to two terms.  One in office.  One in jail."
From: SAMMY@vand.physto.se
Newsgroups: fj.mail-lists.x-window
Subject: xterm & fonts
Date: 27 Jul 92 18:38:01 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: Mon, 27 Jul 1992 17:50 +0200
Message-Id: <5D9285E5804025DA@vand.physto.se>
X-Envelope-To: xpert@expo.lcs.mit.edu
X-Vms-To: IN%"xpert@expo.lcs.mit.edu"


        This is a question that perhaps will only reveal the level of
my ignorance: why can one use only fixed fonts in xterm? What are the
extra problems involved in arranging things so variable character width
fonts can be used? I mean, in such a way that the output looks nice on
the screen.

	Thanks so much in advance.


JCA
sammy@vana.physto.se
From: gerber@solbourne.com (Andrew Gerber)
Newsgroups: fj.mail-lists.x-window
Subject: Wanted: sites for Solaris software testing
Date: 29 Jul 92 03:34:09 GMT
Distribution: fj
Organization: Solbourne Computer, Inc., Longmont, CO

Date: Tue, 28 Jul 1992 21:03:57 GMT
Message-Id: <Bs4AIn.Bvt@solbourne.com>
Newsgroups: comp.unix.solaris,comp.sys.sun.misc,comp.windows.x

We're looking for a few sites which meet the following criteria:

* Currently developing software with Solaris 2.0
* SPARC platforms
* Use X or Open Windows
* Use C, C++, or Fortran
* On the internet or good internet access
* Need a better debugger than the "dbx" and "dbxtool" which come
  with Solaris

If you or your site meet the above criteria, please send us mail.
Include the type of software you're developing, the percentage of time
which you are using Solaris for development, and the number of
developers involved.  Also include your work phone #.

Selected sites will have the chance to use the next generation of
Solbourne's debugger products.

Thanks in advance for your responses.

Andrew Gerber
Solbourne Software Products Division
gerber@solbourne.com
(303) 678-4606
-- 
/-----------------------------------------------------------------/
/ Andy Gerber		     / gerber@solbourne.com               /
/-----------------------------------------------------------------/
From: carson@cs.columbia.edu (Carson A. Gaspar)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Problems with Type1 font support - X11R5p14 SunOs 4.1.2
Date: 27 Jul 92 23:22:19 GMT
Distribution: fj
Organization: Columbia University Department of Computer Science

Date: Mon, 27 Jul 1992 18:51:42 GMT
Message-Id: <1992Jul27.185142.26231@ctr.columbia.edu>
Newsgroups: comp.windows.x


Looking at fix-13, it seems that get_bitmaps and get_extents have been
killed.  All the other font code has just had all references removed,
with no other changes as far as I can tell.

If anyone can tell me what's going on, please do.  For now, I'll just
comment out the offending lines and pray.

-- 
			    Carson Gaspar
			carson@cs.columbia.edu
From: ware@organ.cis.ohio-state.edu (Peter Ware)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Can Primitive widgets be parents?
Date: 28 Jul 92 00:54:00 GMT
Distribution: fj
Organization: Ohio State Computer Science

Date: 27 Jul 92 20:40:37 GMT
Message-Id: <WARE.92Jul27154037@organ.cis.ohio-state.edu>
Newsgroups: comp.windows.x

> Can Primitive widgets be parents?
Any widget can have as many popup children as desired -- it is
primarily a conveniant method of getting properly qualified resource
names.

Also, as long as it is never managed a Primitive widget can have
children created with XtCreateWidget().  For most applications this is
not a useful thing although it is not unreasonable for a widget to
create other widgets this way.

> And in the same page, they create two buttons, but with same widget name
> "button":
>
> Widget button;
>
> button = XtVaCreateManagedWidget("PushMe-1", xmPushButtonWidgetClass, parent,
>            NULL);
> button = XtVaCreateManagedWidget("PushMe-2", xmPushButtonWidgetClass, parent
>            NULL);

This is because the application does nothing further with the "button"
widget.  It would have been just as valid (ignoring error checking) to
write:

	(void) XtVaCreateManagedWidget("PushMe-1", xmPushButtonWidgetClass,
					parent, NULL);

and discard the return value.
--
Pete Ware / Ohio State University /
           ware@cis.ohio-state.edu
           (614) 538-0965
Too bad the Nike slogan isn't "Just Do It Right" instead of "Just Do It"
From: ratinox@splinter.coe.northeastern.edu (Richard Pieri/Stainless Steel Rat)
Newsgroups: fj.mail-lists.x-window
Subject: Re: xcb version 1.0, porting note
Date: 23 Jul 92 07:49:33 GMT
Distribution: fj
Organization: 3WA, Boston Office. Or Nu Meta Chi. Take your pick.

Date: 22 Jul 92 15:02:08 GMT
Message-Id: <RATINOX.92Jul22110208@splinter.coe.northeastern.edu>
Newsgroups: alt.sources.d,comp.sources.d,comp.windows.x

>>>>> On 21 Jul 92 09:27:32 GMT, fbm@ptcburp.ptcbu.oz.au (Farrell McKay)
>>>>> said:

FM> Ok, ok.  A quick note to everybody compiling xcb at home.  The
FM> Makefiles contain a reference to libnsl.a.  Many systems don't have
FM> this library.  Don't panic!  If your compiler complains that it can't
FM> find libnsl.a, just remove that bit.

Yes, it was quite annoying trying to compile under Bugtrix when GCC
complained about not finding the No Such Library :-).

--Rat

||||| | | | |  |  |  |   |   |    |    |    |   |   |  |  |  |  | | | | | |||||
                                                   __        ___ 
Richard Pieri, Northeastern's Stainless Steel Rat/   | /| / /   | The Worlds
Internet: ratinox@meceng.coe.northeastern.edu   /__  |/ |/ / /| | Welfare Works
    UUCP: ...!northeastern.edu!splinter!ratinox/   | /| / / / | | Association:
  BITNET: UA_RLP@NUHUB{.BITNET}               /__  |/ |/ / /  | | I will solve
  USNail: 14 Westdale RD  Holbrook, MA 02343 /   | /| / / /___| | any problem
 ICBMnet: 42 deg 1 min N, 71 deg 0 min W    /    |/ |/ /_//_____| for you.
From: gerard@uwovax.uwo.ca (Gerard Stafleu)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Want DECwindows Customizations (via Resources???)
Date: 30 Jul 92 06:49:06 GMT
Distribution: fj
Organization: University of Western Ont, London

Date: Wed, 29 Jul 1992 19:12:30 GMT
Message-Id: <1992Jul29.151230.1@uwovax.uwo.ca>
Newsgroups: comp.os.vms,comp.sys.dec,comp.windows.x

> Problem 5  Has anyone figured out how to have multiple default
> ~~~~~~~~~  title and icon names that aren't "DECterm <n>"?

Assum that the symbol Pwin has the title in it you want for the window, 
and Picon for the icon:

$ dev_type = F$getdvi("TT","DEVTYPE")
$ IF dev_type .EQ. 112    !DECterm window
$    THEN
$    OSC[0,8] = 157
$    ST[0,8] = 156
$    WRITE SYS$OUTPUT OSC,"21;''Pwin'",ST    !set window name
$    WRITE SYS$OUTPUT OSC,"2L;''Picon'",ST    !set icon name
$ ELSE  ! Something else, presumably Xterm
$    write sys$output "<ESC>]2;"+ "''pwin'" +"^G"
$ ENDIF

[<ESC> is the Escape character]

The ELSE part works for Xterm windows (I don't know if you can do 
icons).  I discovered that that code will hang up a DECterm, hence the 
check on device type.  That is a bit of a workaround, as type 112 is 
something like a VT340.  I don't know of any way to find out if your 
terminal is a DECterm.  Xterms are VT100's, so the trick works.

----
Gerard Stafleu
email: gerard@uwo.ca
CCS, NSC 202, University of Western Ontario,
London, Ontario, Canada N6A 5B7
(519)661-2151
From: whe@usc.edu (Wei He)
Newsgroups: fj.mail-lists.x-window
Subject: Can Primitive widgets be parents?
Date: 26 Jul 92 12:48:33 GMT
Distribution: fj
Organization: University of Southern California, Los Angeles, CA

Date: 26 Jul 1992 01:00:49 -0700
Message-Id: <l74mthINN5q4@phakt.usc.edu>
Newsgroups: comp.windows.x

Hi:
   Can Primitive widgets be parents?
   In O'Reilly Volume Six - Motif Programming Manual p.165, prompt_dlg.c, There
   is a satement:

   dialog = XmCreatePromptDialog(pb, "prompt", args, 2);

   pb is a PushButton, OK, PushButton is a Primitive widget, How can it be the 
   parent of Dialog?

   And in the same page, they create two buttons, but with same widget name
   "button":

   Widget button;

   button = XtVaCreateManagedWidget("PushMe-1", xmPushButtonWidgetClass, parent,
            NULL);
   button = XtVaCreateManagedWidget("PushMe-2", xmPushButtonWidgetClass, parent
            NULL);


   Is this allowed in Motif 1.1?


   Please reply to whe@nunki.usc.edu, Thanks.

scott