HDTenEightyP/NetNews huggingface dataset:
From: Markku.Savela@tel.vtt.fi (Markku Savela)
Subject: Understanding resource value caching...
Organization: Technical Research Centre of Finland
Date: Tue, 13 Oct 1992 21:47:03 GMT
Reply-To: savela@tel.vtt.fi (Markku Savela)


I am a bit confused about following:

  If a resource is a pointer to complex structure, and I declare a
  resource converter that allocates this structure and returns the
  pointer to it as value, ...

  ..now, when the resource is actually associated by widget, how is
  the resource manager to know whether widget made a local copy
  (initialize) of the resource or not? Does it just assume local copy
  is made, thus removing the option of *not* making a local copy of
  complex resource value from the widget makers?

  ..and if I wanted to tell in initialize, whether I made a copy or
  not to the resource manager? How is initialize to know whether the
  resource is a result of resource manager or whether is was just
  supplied by XtSetArg-method directly the XtCreateManagedWidget?

I am asking because I might have *lots* of widgets that would just
default the same resource and making hundreds of identical copies is
not tempting me...

The following are just additional details, a skeleton of how I plan to
set up the resource converter. Declaring it with:

      XtSetTypeConverter(XtRString, XtRMyComplexTypePtr,
        		CvtStringToMyComplexType, NULL, 0,
                        XtCacheAll | XtCacheRefCount,
                        MyComplexTypeDestructor);

And CvtStringToMyComplexType converts the string, allocates some
largish structure...

Boolean CvtStringToMyComplexType(Display *dpy,
                                 XrmValue *args,
                                 Cardinal *num_args,
                                 XrmValue *fromVal,
                                 XrmValue *toVal,
                                 XtPointer *converter_data)
   {
      static XtPointer x;
      ...
      x = XtMalloc(sizeof(MyComplexType);
      ...
      toVal.addr = &x;
      *converter_data = (XtPointer)x;
      return True;
   }


--
Markku Savela (savela@tel.vtt.fi), Technical Research Centre of Finland
Telecommunications Laboratory, Otakaari 7 B, SF-02150 ESPOO, Finland
Newsgroups: comp.windows.x
From: books@fsunuc.physics.fsu.edu (Roger Books)
Subject: Re: Need recommendation for X on IBM-PC (ya, i've been thru' FAQ!)
Organization: FSU nuclear physics
Date: Thu, 15 Oct 92 20:51:38 GMT

In article <GJAMES.160@HUSKY1.STMARYS.CA> GJAMES@HUSKY1.STMARYS.CA (GJames) writes:
>>mece25q@elroy.uh.edu (Pakala, Rama R.) writes:
>
>>>I have gone thru' the FAQ list of X servers for IBM-PCs.  I would like to
>>>hear from netters about their experiences with X servers on IBM-486s. Especially
>>>the problems you have had, if any.
>>>That would help me greatly in choosing  from the list.
>>>Thanks.
>>>Rama Pakala.
>>>mece25q@jetson.uh.edu
>
>>I think DESQview/X is definitely the winner these days.  
>>I believe it's the only full X Window system while all the rest
>>are just X servers for the PC.  I saw the demo in UNIX Expo last
>>October and was really impressed.  I own a copy of the last 
>>version of X11/AT and I sincerely recommend against it. 
>>One more thing: Like almost all other heavy applications, you'll 
>>enjoy it only if you run on a high-end 386/486 PC.
>
>>Ilan Aisic
>
>
>Sure its great if you only want to run in 800x600 in 16 colors. Try running 
>sun net manager and see what happens.
>

This all depends on the video board.  Some video boards do higher resolution.

Roger
books@fsunuc.physics.fsu.edu
Xref: sparky comp.windows.x:17775 comp.windows.x.motif:6772
From: fortress@nic.cerf.net (Fortress Sftwr Desgn)
Newsgroups: comp.windows.x,comp.windows.x.motif
Subject: Need charting widgets...
Date: 13 Oct 92 03:53:45 GMT
Followup-To: comp.windows.x
Organization: CERFnet

Can someone help me find a set of widget class for generating pie, bar,
X-Y, scatter, and other charts from a X11 application.  I would prefer 
source code.  If you know of a site and the specific file name, please
respond.  Your assistance will be highly appreciated.  Send email to
fortress@cerf.net.
From: albrecht@cs.flinders.edu.au (Tony Albrecht)
Newsgroups: comp.windows.x.pex
Subject: PEX shading++
Date: 5 Oct 92 12:12:45 GMT
Organization: Flinders Asylum

Of course I forgot to say what PEX library I'm using..
it's the dec pex library. I'm not sure what version but the docs were written
in 1991. let me know if you need more information.

								-Tony
From: toby@cs.man.ac.uk (Toby Howard)
Newsgroups: comp.windows.x.pex
Subject: Re: NEED HELP! XServer crashes!
Date: 13 Oct 92 16:52:38 GMT
Organization: Department of Computer Science, University of Manchester
In-reply-to: rthomson@mesa.dsd.es.com's message of 13 Oct 92 05:18:29 GMT

SunPHIGS 2.0 has the same problem as PEX-SI, offering colour support only.
Anyone have patches for this for mono support?

Thanks
Toby
--

-----------------------------------------------------------------------
Toby Howard    Department of Computer Science, University of Manchester
Lecturer               Oxford Road, Manchester, M13 9PL, United Kingdom
                                                   Tel: +44 61-275-6274
toby@cs.man.ac.uk                                  Fax: +44 61-275-6236
-----------------------------------------------------------------------
Newsgroups: comp.windows.x.pex,comp.windows.x
From: worthen@nosc.mil (Richard H. Worthen)
Subject: measure/analyze X/PEX protocol over LANs
Keywords: measure X PEX protocol LANs
Organization: Naval Ocean Systems Center, San Diego, CA
Date: Sat, 10 Oct 1992 18:33:43 GMT


I'm looking for tools (equipment and software) to measure/analyze X 
client/server communications over ethernet LANs. I'm especially 
interested in measuring/analyzing client/server communications in 
a PEX protocol environment, i.e., 3-D requests. 

If anyone has info on this subject please respond by email. I 
will consolidate and post the response to the news group.

Thanks in advance,
Rick.
Newsgroups: comp.windows.x.pex
From: hersh@expo.lcs.mit.edu (Jay Hersh)
Subject: Re: NEED HELP! XServer crashes!
Organization: X Consortium, MIT Laboratory for Computer Science
Date: Wed, 14 Oct 1992 00:54:51 GMT

perezc@woods.ulowell.edu writes:

>Hello!

>	I seem to have a very big problem with the X/PEX server we have over
>here.  It's X11R5 with PEX-SI Phigs.  I tried running the examples in Tom
>Gaskins' book and in a lot of cases the server crashes.  The system would
>hang and then log me out.  Is this normal?  

Yes. If the server crashes then the system resets if your server and client
are the same you get logged out because the display manager resets the 
server after the crash. Tom's examples do this to my most up to date
PEX-SI as well. Some stuff he uses just isn't supported, others have
bugs I am trying to track (got interrupted by a bunch of other pressing
stuff).

>	I've been able to get some of the examples running but is's so slow!
>I'm using DECstation 500/120 and it looks slower than an apple II.  Is this
>really how it should be?

This is a software Sample implementation. Basically just a proof of concept. 
No optimization. For 3D if you eant/need performance you gotta get silicon.

Can't comment on the rest...


	Jay Hersh
--
Hopfen und Malz, Gott erhalts
Newsgroups: comp.windows.x.pex
From: perezc@woods.ulowell.edu
Subject: NEED HELP! XServer crashes!
Organization: University of Lowell
Date: Mon, 12 Oct 1992 21:03:41 GMT

Hello!

	I seem to have a very big problem with the X/PEX server we have over
here.  It's X11R5 with PEX-SI Phigs.  I tried running the examples in Tom
Gaskins' book and in a lot of cases the server crashes.  The system would
hang and then log me out.  Is this normal?  

	I've been able to get some of the examples running but is's so slow!
I'm using DECstation 500/120 and it looks slower than an apple II.  Is this
really how it should be?

	I tried using PEXlib from DEC though it compiles only after not
defining MPEX.  I've got PEXtk running too and it seems a lot faster though
in some cases the server crashes.  And in some of the example tests I just
can't figure out what it's supposed to be displaying. 

	Everything looks really full of bugs.  Though I suspect it's because
the Xserver was improperly installed.  Am I correct?  Or is there something
I'm missing.

Carlos

P.S.  I got the PHIGS toolkit running to but it really crawls on my machine.
And yes, the system crashes too.

P^2.S.  I've tried PEXIM and it seems to run fine, except for a minor fault
in some of the provided tests. 

P^3.S.  Anyone outhere who could lend me a hand?
Newsgroups: comp.windows.x.pex
From: joern@imf.unit.no (Joern Amundsen)
Subject: PEX C interfaces
Organization: The Norwegian Institute of Technology, Trondheim, Norway.
Distribution: comp
Date: 13 Oct 92 16:37:08


Due to different shortcomings of the PEX-SI, for instance lack of
monochrome support and lots of other features which are not yet
implemented, what free PEX based options do you have !?

For instance, on contrib there seems to be two C interfaces to the PEX
protocol, the Sun Microsystems Xpex and the DEC dec-pexlib. Anyone
that could comment on these two or other free C protocol interfaces
available ?

I've tried the dec-pexlib myself. Mainly because it seems to be well
documented, (383 page ps file supplied with the source). However,
although the 1 year old contrib version seems to be the newest one as
compared with gatekeeper.dec.com it failed with my X11R5 pl 17 Xdec
server :-(

When running the supplied test program, cube, I got

X Error of failed request:  BadRequest (invalid request code or no such operatio
n)
  Major opcode of failed request:  130 (X3D-PEX)
  Minor opcode of failed request:  128 ()
  Serial number of failed request:  23
  Current serial number in output stream:  29

I would appreciate if anyone at Digital could shed some light on this.
Thank you.

-joern
--
  +---------------------------------------+----------------------------+
  | Joern Amundsen                        | email                      |
  | SINTEF Industrial Mathematics         |  - joern@sima.sintef.no    |
  | Department of Mathematical Sciences   |  - joern@imf.unit.no       |
  | The Norwegian Institute of Technology | phone +47-7-59-2092        |
  | N-7034 Trondheim, Norway              | fax   +47-7-59-2971 / 3524 |
  +---------------------------------------+----------------------------+
Newsgroups: comp.windows.x.pex
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Subject: Re: NEED HELP! XServer crashes!
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Date: Tue, 13 Oct 92 05:18:29 GMT

In article <1992Oct12.160341.1@woods.ulowell.edu>
	perezc@woods.ulowell.edu writes:
>I'm using DECstation 500/120 and it looks slower than an apple II.  Is this
>really how it should be?

No.  The PEX-SI is exactly what it says -- a Sample Implementation.
DEC has a PEX server product and that is what you should be using.
After all, only DEC has all the internal knowledge of their hardware
(graphics boards and CPU stuff) to make 3D rendering run fast.  You
should get DEC's PEX server product and forget the SI.

						-- Rich
-- 
	Repeal the personal income tax; vote Libertarian in 1992.
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer
From: stgprao@st.unocal.COM (Richard Ottolini)
Newsgroups: comp.windows.x.pex
Subject: Re: PEX shading
Date: 7 Oct 92 19:53:11 GMT
Organization: Unocal Corporation

In article <1992Oct05.120753.68030@frodo.cc.flinders.edu.au> albrecht@cs.flinders.edu.au (Tony Albrecht) writes:
>I'm trying to implement a PEX extension to the InterViews 3.1 toolkit as 
>an honours project but am having trouble doing any sort of shading. I have 
>access to two different servers, one which only has the PEX Sample 
>Implementation, the other which has a more substantial implementation.
>
>  Everything works fine until I try to shade.
>I've set up a lightLut with all the relevant data (dirn,type,colour), set the
>surfaceinterp method to dot product, I think I've set the lightsourcestate
>correctly and set the reflection model to diffuse.
>   The best result I can get is black objects. I did at one stage get a black
>object with some sort of filling bug which produced an extraneous polygon
>which DID change colour when moved, so something must have been done right.

The MIT PEX-SI does not implement lighting models.
You may have that vrsion or a close descendant.
Newsgroups: comp.windows.x.pex
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Subject: Re: Support for monochrome
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Date: Mon, 12 Oct 92 20:32:35 GMT

In article <12805@privet.rl.ac.uk>
	ls@inf.rl.ac.uk (Lakshmi Sastry) writes:
>Has anybody got a patch for the PEX-SI that will enable it to
>support monochrome? If so, can you send me the patch, please?

I'm not aware of any such patch, although it is often requested on
this newsgroup.  Just how much work would it be to patch the SI support
a 1-bit display?  Can anyone who worked on the PEX-SI give us a
ballpark guess?  There might be some students who would be willing to
do the job if they knew the size of the task.

						-- Rich
-- 
	Repeal the personal income tax; vote Libertarian in 1992.
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer
Newsgroups: comp.windows.x.pex
From: bruschke@braque (Michiel Bruschke)
Subject: PEX Color selection
Organization: Department of Mechanical Engineering/University of Delaware
Date: Thu, 8 Oct 1992 06:05:20 GMT


I am trying to plot a shaded 3-D surface with colour contours. The 
contours need to be in a intuitively logical order. Right
now I am setting up the colors by choosing HSV values. I set the
Saturation and Value to .95 and sweep Hue from blue to red.
I then convert the HSV values to RGB using an algorithm from
Foley and van Dam "Fundamentals of Interactive Computer Graphics".

The problem is that I end up with a number of colors that are hard
to distinguish in the green range (with only 11 contours). 
I tried skewing the Hue sweep, but that results in shifting the problem 
to the reds.

Does anybody have a better algorithm for setting up an arbitrary
range of colors ? An algorithm that would also vary the
saturation would probably offer some improvement.

Any thoughts/suggestions are greatly appreciated
Thanks,

mike

P.S I am using SunPHIGS 2.0
From: albrecht@cs.flinders.edu.au (Tony Albrecht)
Newsgroups: comp.windows.x.pex
Subject: PEX shading
Date: 5 Oct 92 12:07:53 GMT
Organization: Flinders Asylumn

I'm trying to implement a PEX extension to the InterViews 3.1 toolkit as 
an honours project but am having trouble doing any sort of shading. I have 
access to two different servers, one which only has the PEX Sample 
Implementation, the other which has a more substantial implementation.

  Everything works fine until I try to shade.
I've set up a lightLut with all the relevant data (dirn,type,colour), set the
surfaceinterp method to dot product, I think I've set the lightsourcestate
correctly and set the reflection model to diffuse.
   The best result I can get is black objects. I did at one stage get a black
object with some sort of filling bug which produced an extraneous polygon
which DID change colour when moved, so something must have been done right.

   Can someone help me here?
   Some sample code would much appreciated.
   ANY help would be much appreciated.

Thanks,
								-Tony
Newsgroups: comp.windows.x.pex
From: hersh@expo.lcs.mit.edu (Jay Hersh)
Subject: Re: Support for monochrome
Organization: X Consortium, MIT Laboratory for Computer Science
Date: Wed, 14 Oct 1992 00:52:19 GMT

rthomson@mesa.dsd.es.com (Rich Thomson) writes:

>In article <12805@privet.rl.ac.uk>
>	ls@inf.rl.ac.uk (Lakshmi Sastry) writes:
>>Has anybody got a patch for the PEX-SI that will enable it to
>>support monochrome? If so, can you send me the patch, please?

>I'm not aware of any such patch, although it is often requested on
>this newsgroup.  Just how much work would it be to patch the SI support
>a 1-bit display?  Can anyone who worked on the PEX-SI give us a
>ballpark guess?  There might be some students who would be willing to
>do the job if they knew the size of the task.

It actually shouldn't be too much work (though it won't even make
it onto my priority list), look in the file miConvert.c in the directory
/extensions/server/PEX/ddpex/mi/level2  of the SI  server.

--
Hopfen und Malz, Gott erhalts
Newsgroups: comp.windows.x.pex
From: yang@mtu.edu (Xiaoyang Yang-grad)
Subject: FAQ needed
Organization: Michigan Technological University
Date: Thu, 15 Oct 1992 23:43:27 GMT

i just started to learn PEX stuff.   could any one who organizes this
group give me files containing FAQ and answers?  or, any other idea/
suggestion/advivce for a new user of PEX are welcomed.

thanks in advance.


yang
-- 
============
my signature
============
Newsgroups: comp.windows.x
From: villagra@dit.upm.es (Victor A. Villagra)
Subject: How to set a watch cursor in ALL the shells??
Keywords: watch cursor, application shell 
Organization: Dept. Ingenieria de Sistemas Telematicos, UPM, Madrid, Spain.
Date: Wed, 14 Oct 1992 11:10:33 GMT


Hi, we have an application which may have a lot of shells under the
top-level shell and what we want to do, is to set a watch cursor in ALL the
application windows, not only in the top-level, ignoring device events in
all the application windows.

I have tried the code in the FAQ (#126), but it seems to work only in the
top-level shell. 

Is there a method to do this, other than keeping in an up-to-date array of
all the shells used in the application and apply the method to each one ??

//Victor.

--
Victor A. Villagra         |  tel: +34 1 5495762, x-447
Dpt. Ing. Telematica       |  fax: +34 1 5432077
E.T.S.I. Telecomunicacion  |  RFC-822:  villagra@dit.upm.es
Ciudad Universitaria       |  X.400  :  C=es; A=mensatex; P=iris; O=upm;
E-28040  MADRID (SPAIN)    |            OU=dit; OU=cactus; S=villagra
From: ucjtrjf@ucl.ac.uk (Jonny Farringdon)
Newsgroups: comp.windows.x
Subject: Re: xnews server crashing
Date: 16 Oct 92 14:03:50 GMT
Organization: Bloomsbury Computing Consortium

Audrey, i've an xnews / XsunMono testimonial to mail you relevant
to machine with small memory (8MB).

BUT  your post produced a nonexistant reply address and you didn't
give an alternative .... strauss@melpar  not realy very helpfull ;-)

J.  ucjtrjf@ucl.ac.uk
Newsgroups: comp.windows.x
From: hue@island.COM (Pond Scum)
Subject: Re: 24-bit graphics in XView -- help!
Organization: Island Graphics Corp.
Date: Fri, 9 Oct 1992 05:53:25 GMT

johnc@crsa.bu.edu (John Collins) writes:

>I have been trying to create an XView canvas that is able to 
>display a 24-bit image.  The problem is that when I use xv_create
>to make a canvas, it is created with the depth of its parent
>by default.  And the top-level window of the application 
>automatically gets the default depth of the root window - which
>is 8 in my case, even though the screen is able to support the
>TrueColor visual.  I can find no mention of how to get around
>this problem in the O'Reilly manuals.  Anybody have any suggestions?

This probably belongs in comp.windows.open-look.

Well, one way to get this to work is to just type "-visual TrueColor"
or "-depth 24" (or both) on the command line.  If you call xv_init()
with XV_INIT_ARGC_PTR_ARGV then this should work.  The other way is just
to specify XV_VISUAL and XV_DEPTH when you create the canvas.  All this
stuff is all in the manuals (XView 3).  If you're using XView 2, good
luck.  I've done it but I had to look at the Xview sources to figure
out how to get it to work.

-Jonathan		hue@island.COM
Newsgroups: comp.windows.x
From: rsmith@proteus.arc.nasa.GOV (Roger Smith -- IAS)
Subject: Killing all clients on exit, on an X-terminal
Organization: The Internet
Date: Fri, 9 Oct 1992 00:12:28 GMT

The LAST line in your .Xsession file should be something like:

exec /usr/bin/X11/xterm -title Console -font 6x10 -iconic -C -geometry 80x24+0+290 -name console -xrm "*iconGeometry:+0+521" -ls

The above line creates an ICONIFIED xterm window named "Console".
Since this window was "exec'd", when you exit this window all other
clients of that session will also die. Note also that the "-C" causes
all messages directed to the system console to go to this window...
Maybe not what you want for all situations. Include it or leave it out
to suit.
------------------------------------------------------------------
Roger Smith
Sterling Software at
NASA-Ames Research Center
rsmith@proteus.arc.nasa.gov
- 
If change is -- inevitable -- predictable -- beneficial -- 
doesn't logic demand that you be a part of it?
One man cannot summon the future. But one man can change the present!
    -- Kirk and the Alternate Spock, "Mirror, Mirror," stardate unknown
+
From: erg@ulysses.att.com (Emden R. Gansner)
Newsgroups: comp.windows.x
Subject: Protocol question on depths
Keywords: Depth RS6000 Protocol
Date: 13 Oct 92 19:38:13 GMT
Organization: AT&T Bell Laboratories

On IBM RS6000 machines (grayscale and color), the list
of allowed depths for a screen only has one item, corresponding
to either a depth of 4 or 8. In particular, depth 1 is not
listed. The X protocol (under Screen Information in the 
Connection Startup section) states that "A pixmap depth of one
is always supported and listed,..." The people at IBM respond,
"Since depth 1 is always supported, there is no reason to list
it for each screen." Is this an acceptable interpretation of
the protocol?
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.windows.x
Subject: Re: Multiple XOpenDisplays on the same display
Date: 9 Oct 1992 21:54:37 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
NNTP-Posting-Host: telecaster.think.com

In article <1992Oct09.113229.26461@watson.ibm.com> mcintyre@owgvm0.vnet.ibm.com (Dave McIntyre) writes:
>The XOpenDisplay calls return different values for the same display.

This is reasonable.  On the client, a "display" is an independent
connection to a display.  Each call to XOpenDisplay() should create a new
one.

>Windows created on any of these displays appear in XQueryTree listings
>for any of the other displays (on the same actual display).

XQueryTree() is returning data about the server's state.  All the windows
are on the same X server display screen, so they should all appear in the
same tree.  In addition, you'll see windows from completely unrelated
clients.

>Events in a window only get sent to the actual display it was created with
>(not any of the "shadow" displays).

The server doesn't know that all these connections are to the same client;
as far as it's concerned, all client connections are created equal.  Thus,
each of these connections defines a new client (which happen all to be
running in the same process).

>Even though the window is listed in a display's XQueryTree, XSelectInput'ing
>with a shadow display on a window causes an XError.

This should work.  Note, however, that some events are restricted so that
only one client can select on them.  This includes multiple clients in the
same process.

>I guess I'm looking for ammunition to support my argument that this is a
>lousy way of selecting events from windows.

It's got some overhead, but it also has some features.  If each window is
opened on a separate display, then XKillClient can be used to kill a window
without affecting any of the other ones (so long as you install an XIOError
handler that doesn't exit).

Without understanding why the program did this, it's hard to form a more
detailed opinion on whether it's a good way to design the program.  All
things being equal, though, I suspect it's not.
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar