HDTenEightyP/NetNews huggingface dataset:
From: baileyc@ucsu.Colorado.EDU (Christopher R. Bailey)
Newsgroups: fj.mail-lists.x-window
Subject: Need stripchart like widgets
Date: 16 Dec 92 16:59:42 GMT
Distribution: fj
Organization: University of Colorado, Boulder

Date: Tue, 15 Dec 1992 19:09:49 GMT
Message-Id: <1992Dec15.190949.5441@ucsu.Colorado.EDU>
Newsgroups: comp.windows.x


I have a strange widget request.  I would like a widget just like the Athena
stripchart widget, but that automatically updates itself some other way.

This sounds wierd, but here's the deal.  My program doesn't use XtAppMainLoop.
It receives all of it's events using signal I/O (basically my signal handler
is a custom XtAppMainLoop).  It works pretty well, but the stripchart widget
never calls it's getvalue function, so it never updates.  I need some other
way for it to be able to call this function.  I am a beginning Xt programmer,
so I thought I'd look for a solution before attempting to modify the Athena
stripchart widget.  Any suggestions or direction would be helpful.  I cannot
use Motif stuff, I need Athena or otherwise freely distributable widgets.


-- 
Christopher R. Bailey            |Internet: baileyc@dendrite.cs.colorado.edu
University of Colorado at Boulder|CompuServe: 70403,1522
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Ride Fast, Take Chances!
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: fj.mail-lists.x-window
Subject: Re: trouble with xmodmap
Date: 18 Dec 92 02:29:24 GMT
Distribution: fj
Organization: McGill Research Centre for Intelligent Machines

Date: 17 Dec 92 21:49:20 GMT
Message-Id: <1992Dec17.214920.6007@thunder.mcrcim.mcgill.edu>
Newsgroups: comp.windows.x

In article <1992Dec14.132813.19208@uropax.contrib.de>, thomax@uropax.contrib.de (Thomas Kaulmann) writes:

> i still stuck in the problem to assign an alt key combination with
> xmodmap.  i've tried to assign the at-sign (@) to the alt-q
> combination using this statement:

> % xmodmap -
> keycode 61 q Q at
> <EOF>

> whats wrong with that??

Nothing.  It's not enough by itself, though.  You also need to make
sure that the Alt key sets the group modifier.  What is the group
modifier, you ask?  Here's a quote from the protocol document;
bracketed text [] is mine:

	Switching between groups is controlled by the KEYSYM named MODE
	SWITCH [sic - actually Mode_switch], by attaching that KEYSYM
	to some KEYCODE and attaching that KEYCODE to any one of the
	modifiers Mod1 through Mod5.  This modifier is called the
	``group modifier''.  For any KEYCODE, Group 1 [the first two
	columns of the xmodmap table] is used when the group modifier
	is off, and Group 2 [the second two columns] is used when the
	group modifier is on.

For example, you might do

xmodmap - << EOF
keysym Alt_L = Alt_L Mode_switch
add Mod5 = Mode_switch
EOF

if nothing else is using Mod5.

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu
From: david@breslau.ap.mchp.sni.de (David Smyth)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Q: Wcl2.3 experimental external interface?
Date: 14 Dec 92 17:53:35 GMT
Distribution: fj
Organization: Siemens-Nixdorf AG

Date: 14 Dec 1992 14:53:10 GMT
Message-Id: <1gi74mINNpd0@horus.ap.mchp.sni.de>
Newsgroups: comp.windows.x

jay@vnet.ibm.com writes:
>I'm looking for more information about the experimental external interface
>mentioned in Wcl23.Announce.
>
>A colleague of mine created a handy tool called ``mish'' (Motif Interface
>SHell) based on tcl 4.0 and wcl 1.06, I believe.  It was used to prototype
>a lot of interfaces but those interfaces were eventually rewritten in C and
>mish ended up laying on the shelf.

This type of tool is the intended client of the "experimental external
interface" mentioned in Wcl23.Announce:

    o   Experimental external interface to the LateBinder mechanism, which
        is intended to support people using Wcl to provide interfaces to
        interpretive environments (like perl).

The external interface to the late binder mechanism remains identical for
Wcl 2.4 (released Friday).

I suppose the best place to look for information on the Late Binder is
WcLateBind.c and WcCreateP.h and WcCreate.h.  Especially, read the comments
titled "Experimental External Interfaces to WcLateBinder" in WcCreateP.h.

The basic idea is to allow all callback invocations to be intercepted
by a client (such as "mish") and sent to an interpreter (like tcl or
perl or...).  Wcl uses this interception to resolve methods: The Wcl
Late Binder looks to find the object to be manipulated by a given
method invocation.  The late binder uses the callback name and object
class name to find the object and invoke the appropriate callback method.

The Hook function, registered with Wcl using WcAddLateBinderHook(),
gets a WcLateBind object to use to resolve the callback.

NOTE: Actions are not directly supported with the late binder.  You
can, of course, provide actions which invoke callbacks...

---------------------------------------------------------------------------
David E. Smyth			David.Smyth@ap.mchp.sni.de
Object/X Researcher		AP 154, Carl-Wery-Str 22, Munich 83 Germany
	Research Grant provided by Esprit Investments Ltd, 
	major sponsor Siemens Nixdorf Informationssysteme AG
From: dwb@IMD.Sterling.COM (David Boyd)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Looking for tools for testing X applications
Date: 11 Dec 92 23:53:51 GMT
Distribution: fj
Organization: Sterling Software

Date: 11 Dec 92 15:03:48 GMT
Message-Id: <1992Dec11.150348.2937@sparky.imd.sterling.com>
Newsgroups: comp.windows.x

In article <1992Dec10.013202.10746@newsgate.sps.mot.com>,
dichter@chdasic.sps.mot.com (Carl Dichter) writes:
|> 
|> In article <3999@cvbnetPrime.COM>, abel@sparc2.prime.com (Barry Abel)
|> writes:
|> |> Does anyone know of good software that can be used to automate the
|> |> testing of an X Windows application?
|> Perhaps some net.people would like to follow-up with thier comments on
|> these tools, as well as corrections/additions.
|> 
Here is an addition to the list:
	
Vendor:      Segue Software, Inc
Phone:       (617)969-3771
Product:     QA Partner
Description: QA Partner is a powerful, multi-platform, automated testing
solution designed specifically for the GUI environment.  Using a true object
oriented language, test scripts can be developed that operate on screen controls
as logical GUI objects, not screen locations. Additional detail on the approach
is available in an article published in The X Resource, Issue 3.

My only affiliation with Segue is as a QA Partner user.  

As an aside, I highly reccomend the use of Purify from Pure software in
conjunction with any testing.  Our rule on the current project is that the
code is done until Purify has sung.


-- 
David W. Boyd	             UUCP:     uunet!sparky!dwb
Sterling Software IMD        INTERNET: dwb@IMD.Sterling.COM
1404 Ft. Crook Rd. South     Phone:    (402) 291-8300 
Bellevue, NE. 68005-2969     FAX:      (402) 291-4362
From: shawn!root@bloom-beacon.MIT.EDU (Mark Jeghers -- UNIX/X/Motif Contractor)
Newsgroups: fj.mail-lists.x-window
Subject: Any news on shared libs in XFree86 (particularly ISC) ?
Date: 14 Dec 92 09:29:19 GMT
Distribution: fj
Organization: Mark Jeghers -- UNIX/X/Motif Contractor

Date: Mon, 14 Dec 92 07:21:13 GMT
Message-Id: <1992Dec14.072113.1517@shawn.uucp>
Newsgroups: comp.windows.x,comp.unix.sysv386

The title says it all.  Last I heard it was in the works but would take
a while.  It is an exciting prospect to me, key to the viability of
X in 386 UNIX environment.  MIT should have rolled in the shared lib
support that was out there for R4.  The R5 release for 386's from MIT,
with assembly optimizations cut from the server, shared libs cut from
the client libs, is totally undesirable to me.  My R4 installation is 
fast and lean.  The MIT R5 for 386's is slower and fatter.  Since I
lack some low-level functions for I18N anyway, why bother?

By the way, all you XFree86 folks, keep up the good work!  In this
matter, you guys look a lot like the cavalry coming to the rescue...

Mark Jeghers
UNIX/X/Motif Contractor
408/281-4823 [voicemail]
From: mahan@TGV.COM (Patrick L. Mahan)
Newsgroups: fj.mail-lists.x-window
Subject: RE: DECWindows questions...
Date: 18 Dec 92 09:11:58 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date:    Thu, 17 Dec 92 23:31:40 PST
Message-Id: <921217233140.26c00291@TGV.COM>
X-St-Vmsmail-To: ST%"xpert@expo.lcs.mit.edu"

#
#I have just started working with DECWindows* (after a few years of Motif* on a
#SUN*).  Two things frustrate/puzzle me.
#
#(1) How do you bring a DECterm up on a remote server. We have logins limited to
#    two on our DEC system.  I get invalid parameter errors when I try to run
#    sys$system.
#

To display a DECterm on a remote X server, issue the following commands from
DCL -

	$ SET DISPLAY/CREATE/NODE=SERVER/TRANSPORT=your-favorite-transport
	$ CREATE/TERM/DETACH

where SERVER is the node|host name of the X server and your-favorite-transport
is either DECnet or TCPIP

#
#(2) What is XUI. Who supports and maintains the standard.  Should I use this
#    instead of Motif (for a large program written already in XUI).  How do
#    I mix Motif and XUI?
#

XUI stands for X User Interface which was originally developed by Digital as
part of DECwindows and went on to form part of Motif.  XUI support is nolonger
being provided for future releases of VMS.  You should instead use DECwindows/
Motif.

Unfortunately, you cannot mix widgets from different widget sets due to
inheritance issues, etc.  However, Digital provides conversion tools to convert
XUI applications to Motif.

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
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Why the program cannot work?
Date: 18 Dec 92 02:34:38 GMT
Distribution: fj
Organization: McGill Research Centre for Intelligent Machines

Date: 17 Dec 92 21:41:30 GMT
Message-Id: <1992Dec17.214130.5583@thunder.mcrcim.mcgill.edu>
Newsgroups: comp.windows.x

In article <1992Dec14.112849.21727@sparc4.ncu.edu.tw>, u438813@imux120.ncu.edu.tw (Lin Wei-Ting) writes:

> 	ximage=XCreateImage(theDisplay,theVisual,theDepth,ZPixmap,
> 						0,0,width,height,8,0);
> 	ximage->data=(char *)malloc(sizeof(char)*width*height);
> 	ximage=XGetImage(theDisplay,xwin,0,0,width,height,AllPlanes,ZPixmap);

You don't need to XCreateImage or malloc data space; XGetImage deals
with creating all aspects of the image.  (Besides, your call to
XCreateImage contains a lurking nonportability: the second zero should
be cast to (char *), unless you don't care about portability to
environments where there's no prototype for XCreateImage.)

> 	for(i=0;i<height;i++)
> 		{
> 		data1=(char *)(ximage->data)+i*width;

data1 undeclared (first use this function)

> 		for(j=0;j<width/2;j++)
> {  k=*(data1+j);  *(data1+j)=*(data1+width-1-j);
>    *(data1+width-1-j)=k; }

You're assuming (a) each pixel is stored in one char and (b) that the
scanlines are adjacent in memory.  Neither one is necessarily the case.

> I want to flip an image horizontally.  But the program cannot work.
> Why?

Assuming you tack enough additional stuff onto the above to turn it
into a program (eg, main(), and some X setup), you'll need to declare
data1 somewhere.  Since you don't say what goes wrong, it's hard to say
much more.  Does it core dump?  Does it flip the image vertically
instead of horizontally?  Does it fail to compile?  Does it kill your
window manager?  Does it kill your cat?  What?

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu
From: dy@duke.cs.duke.edu (Doreen Yen)
Newsgroups: fj.mail-lists.x-window
Subject: TAE+ ver. 5.1 GUI Builder
Date: 11 Dec 92 18:36:47 GMT
Distribution: fj
Organization: Duke University Computer Science Dept.; Durham, N.C.

Date: 11 Dec 92 13:35:27 GMT
Message-Id: <724080926@lear.cs.duke.edu>
Newsgroups: comp.windows.x,comp.windows.x.apps,vmsnet.misc


  Earlier this Fall somebody posted an inquiry about TAE+ from NASA Goddard
Space Flight Center and distr. from COSMIC at U. Georgia.
  I've run the tutorial under VAX VMS 5.5 using their version 5.1 (5.2 is
said to be ready for UNIX boxes with VMS to update Spring '93).  
  While most GUI front ends are $2000 to $9000, this lists for under $1000
with sig. discount for gov. sites.
  The tutorial creates 2 windows with quit pushbuttons.  One has a radio box
and a small bar graph.  The other has a few keyin text fields.  The rehearsal
mode is nice and the whole thing is easily created.  Now the code generator
cranked out about 800 lines of .c and .h then the compile and link created an
executable of 1409 blocks, that's 700Kbytes.  I should mention the compiler
where this happened is VAX C, version 3.1 and also that I expect to be
working elsewhere soon so I won't have much further info. for you on TAE+.
The documentation is 5 inches thick and readable...  Well for this place
that has no money for software tools, is short on computer people and has
the better part of a gigabyte of disk avail., TAE+ may be okay.  If that
sounds like you, mail to service@cossack.cosmic.uga.edu
  Since the software is developed on UNIX, I'd enjoy hearing about the
code generation there, to keep my opinions in perspective.
Doreen

-- 
Doreen Yen			UUCP: ..!{ihnp4,decvax}!duke!dy
				CSNET: dy@duke
				ARPA:  dy@cs.duke.edu
"Have a Happy Year of the Monkey"
From: MCMILLAN@cqm.co.uk ("Brian A McMillan (44) 5057 5388")
Newsgroups: fj.mail-lists.x-window
Subject: Using many colours in ScrolledList.
Date: 14 Dec 92 15:03:32 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Message-Id: <9212141425.AA28446@expo.lcs.mit.edu>
Date: Mon, 14 Dec 92 14:19 GMT


I am building a little events recorder that is supposed to use colour to 
indicate priority/severity. Fine I thought just use XmList and build a 
display rather like the DEC cluster Console thing however reading up on 
it I find that people say it can't be done. (Dan Heller p 428/Vol6 of O'Reilly)

Can anyone tell me how I can either overcome this or otherwise achieve the same
effect?

Brian
===============================================================================
Colloquium - Online VAX Notes usenet archives.
===============================================================================
From: TRANLE@INTELLICORP.COM (Minh Tran-Le)
Newsgroups: fj.mail-lists.x-window
Subject: X11R5 Xmips on riscos-4.52
Date: 13 Dec 92 18:41:31 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Message-Id: <9212131755.AA20558@expo.lcs.mit.edu>
Date: Sun, 13 Dec 92 09:55:13 PST
Reply-To: tranle@intellicorp.com

Has anybody succeeded to build the Xmips for riscos-4.52b from the mit's
x11 r5 sources ?

I have tried to build it after having applied the patches for the ddx/mips
found in the contrib directory of the export.lcs.mit.edu server.  Everything
seems to compile ok but I get a server that make the color monitor loose
sync.

I am trying to use it on a mips r3030 with riscos 4.52b.

Thanks,
Minh Tran-Le.
-------
From: toml@marvin.boulder.ParcPlace.COM (Tom LaStrange)
Newsgroups: fj.mail-lists.x-window
Subject: Re: olvwm 3.3 now available
Date: 14 Dec 92 16:02:50 GMT
Distribution: fj
Organization: ParcPlace Boulder

Date: Mon, 14 Dec 1992 13:44:42 GMT
Message-Id: <Bz94uK.DHq@boulder.parcplace.com>
Newsgroups: comp.windows.open-look,comp.windows.x

In article <SMARTIN.92Dec9132724@torsys02_1.uucp>, smartin@Canada.lsil.com (Stephen Martin) writes:
|> Since olvwm now supports Xpm, does this mean that if an application has a
|> icon defined that has a greater depth than 1, it will display it?


The ICCCM states that icon pixmaps should be of depth 1 (section 4.1.2.4).
If you need a multi-color icon, use an icon-window.

--
Tom LaStrange        toml@boulder.ParcPlace.COM
From: dkarr@sierra.com (David Karr)
Newsgroups: fj.mail-lists.x-window
Subject: Re: keyboardFocusPolicy problem
Date: 12 Dec 92 15:02:21 GMT
Distribution: fj
Organization: Sierra Geophysics,  Kirkland WA

Date: 11 Dec 92 19:51:22 GMT
Message-Id: <1992Dec11.195122.27511@sierra.com>
Newsgroups: comp.windows.x

Self-followup:

I've discovered that this problem only occurs if the application was built
on the HP.  I tried running the application built on the Sun (Motif from
ICS, I believe), and displaying on my 700/RX, and it does not display the
problem.

(I suppose this would have been better directed to comp.windows.x.motif and
comp.sys.hp.)

--
David M. Karr
Sierra Geophysics, Inc.
ARPA: dkarr@sierra.com, UUNET: uunet!sgihbtn!dkarr
Phone: (206) 822-5200 (x343)
From: jcb@hal.com (Joe Beall)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Modality
Date: 12 Dec 92 02:15:19 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: Fri, 11 Dec 92 19:46:12 CST
Message-Id: <9212120146.AA14697@austin4>

> Date: Mon, 7 Dec 92 11:32:10 +0100
> From: devuns@alsys.fr (Olivier Devuns)
> To: xpert@expo.lcs.mit.edu
> Subject: Modality
> 
> I have a Motif-based application where, in some cases, a question or a
> value is asked for via a MessageDialog. Those questions or values are
> very important (the app cannot continue without), thus the MessageDialogs
> used there are modal (I should even say FULL_APPLICATION modal). The
> problem I have now is to attach help facilities to those modal dialogs. My
> help window (an independent TopLevelShell) is of course affected by the
> modality.
> The user is able to bring it up using the "Help" button in the modal dialog,
> but since the dialog was MODAL, (s)he is unable to play efficiently with help
> (scroll, etc...), because all input still goes exclusively to the Modal
> dialog.
> 
> How can I do so that the help window is not affected by the modal state of the
> rest of the application ?

I didn't see a response to this, so here's one:

I have solved this problem in the past by having a library routine
produce the help window after checking for the parent window's (shell-level)
modality.  If a normal secondary window, then the routine provides a
normal secondary help window (dialog shell); if the requestor is a modal
popup, then the routine provides a modal help window. In these cases, the
widget tree is the same, but the type of modality is set programmaticly.

Once the help window is created, of course, and the same object is to be
used for all help requests, then the window has to be unmanaged and remanaged,
I believe, in order for the change to modality to take effect.  Maintain an
internal/static variable or etc. to keep track of what it is, then you can
determine for each request whether this added step is necessary.

If the help window can remain mapped indefinitely, you would have to unmanage
it temporarily to convert it to a modal popup.  Alternatively, you could
create a separate class for "modal" help information related to "alert"
popups.

Using a modal help window where needed resolves the problem of access, and
it seems acceptable that the help window requires dismissal with the modal
parent.
From: dov@menora.weizmann.ac.il (Dov Grobgeld)
Newsgroups: fj.mail-lists.x-window
Subject: xdvi grey-scale antialiasing problem
Date: 14 Dec 92 16:52:10 GMT
Distribution: fj
Organization: Weizmann Institute of Science, Computation Center.

Date: 14 Dec 92 12:30:17 GMT
Message-Id: <1992Dec14.123017.8788@wisipc.weizmann.ac.il>
Newsgroups: comp.windows.x

Has anyone got the grey-scale anti-aliasing option of xdvi working?
I get xdvi to compile and run with the -DGREY flag, but I don't
get any grey-scale anti-aliasing. Instead the characters are displayed
in fg color with a bg frame frame around them. My guess is that the
color allocation is failing.

I have tested this both on an RS/6000 running AIX 3.1.5 with MIT X11R5
libraries and on HP-UX 8.05 also with MIT X11R5 libraries. I get the
same result on both, and the same result on all X-servers I have tested.

--
                                                        ___   ___
                                                      /  o  \   o \
Dov Grobgeld                                         ( o  o  ) o   |
The Weizmann Institute of Science, Israel             \  o  /o  o /
"Where the tree of wisdom carries oranges"              | |   | |
                                                       _| |_ _| |_
From: rob@spot.Colorado.EDU (Rob Cuthbertson)
Newsgroups: fj.mail-lists.x-window
Subject: John Bradley's current location?
Date: 14 Dec 92 18:34:33 GMT
Distribution: fj
Organization: University of Colorado, Boulder

Date: 14 Dec 92 14:54:49 GMT
Message-Id: <1992Dec14.145449.17087@ucsu.Colorado.EDU>
Newsgroups: comp.windows.x


John Bradley, the author of xv (version 2.21 released 5/92) lists his home
as bradley@cis.upenn.edu  Alas, this machine doesn't seem to be around any-
more, and upenn.edu doesn't seem to know anyone named "bradley"

Does anyone know where John can be found?  I'd like to use a large chunk of
the xv code in an independent study project (NOT for re-release) and I'd like
his permission first.

Reduce, reuse, recyle, conserve bandwidth.  Send me email, if anyone asks I'll
send summaries.

--Rob Cuthbertson, rob@spot.Colorado.EDU
Project: World Peace
no plan.
From: juando@cnm.us.es (Juan Domingo Martin Gomez)
Newsgroups: fj.mail-lists.x-window
Subject: Re: X Terminal screen locker
Date: 16 Dec 92 21:12:49 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: Wed, 16 Dec 92 20:57:21 +0100
Message-Id: <9212161957.AA23880@sparc1.cnm.us.es>

In article <1992Dec16.122101.2985@sth.frontec.se>, bjst@sth.frontec.se
(Bjorn Stenberg) writes:
>
>Hi, I've got a small security problem.
>
>How do I get a screen locker working for my X terminals?
>When running xlock, it tells me:
>
>    xlock: can't lock <displayname>'s display
>
>...which (notably) is different from the message I get when trying to
>lock a secured display (xlock: unable to open display xxx).
>This leads me (non X guru) into thinking there's something special about
>X terminals apart from the security authorization.
>

Yes, it is a differnt problem, but there is nothing special about X
terminals.  The problem is in xlock itself. It won't lock a display which
is not local.  This is an attempt to avoid someone locking some other
person's display. I think the problem is not solved because you can still
log into that machine, set the display and run xlock (as long as access is
allowed to any X client).  Of course no one can "log into an X terminal",
so you can't lock them using an unmodified xlock.

>I've browsed the FAQ (kudos to David and the guys for a really great FAQ!)
>but although it answered a lot of my other questions, this one remains
>unsolved.
>
>Any hints are appreciated.
>

You'll have to do some hacking into xlock, but it is not difficult. I can send
you an already hacked version if you want.

Hope it helps,

Juan
-- 
Juan D. Martin                     Centro Nacional de Microelectronica
<juando@cnm.us.es>                                   Edificio C.I.C.A.
Phone: 34-5-4623811                             Av/ Reina Mercedes s/n
Fax:   34-5-4624506                               41012-SEVILLA, SPAIN