HDTenEightyP/NetNews huggingface dataset:
From: dwd@cbnewsc.cb.att.com (David W. Dykstra)
Subject: Re: How do I tell Motif where to position my TopLevelShell?
Organization: AT&T
Date: Wed, 23 Dec 1992 23:06:00 GMT

> When I run the following code to create a new topLevelShell, the
> location (position) of the window is done by Motif - it ignores my XmNx
> and XmNy arguments completely.  Does anyone know how to specifically
> place a topLevelShell?  I've checked the FAQ and about a year's worth of
> past postings, no luck.  Also note that XmNdefaultPosition doesn't
> affect it. Thanks.
> 
> -------------------------------
> ac = 0;
> XtSetArg (al[ac], XmNx, sx);  ac++;
> XtSetArg (al[ac], XmNy, sy);  ac++;
> XtSetArg (al[ac], XmNwidth, 50);  ac++;
> XtSetArg (al[ac], XmNheight, 100);  ac++;
> top = XtAppCreateShell("x", "x", applicationShellWidgetClass,
> 				XtDisplay(w), al, ac);
> XtRealizeWidget(top);
> -------------------------------

I've had success with both setting the geometry resource and with setting
x and y after the top level shell is created.  I set the geometry resource
before the widget is managed and set x and y to move things later.  I'm
not sure anymore if those are the only ways that work but I think so.

The bad thing about setting x and y after the window is managed is that
those values don't include the window manager border.  I have to go
through a lot of trouble to find the window that the window manager has placed
around mine and determine its size in order to figure out what x and y
I really want.

- Dave Dykstra
  dwd@graceland.ih.att.com
Newsgroups: comp.windows.x.motif
From: davidd@ctsx.celtech.com
Subject: prob with making xrolodex
Date: Mon, 28 Dec 1992 16:04:00 GMT
Organization: Cellular Technical Services, Seattle

machine: HP 9000/837 HP-UX 8.02, standard cc compiler, Motif 1.1,
GNU make

Hello, I pulled off xrolodex from the contrib dir on export and
was trying to make it this morning and I got the following: 

ctshp> gmake all
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c xrolo.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc: Optdriver: Bad optimizer option; ignored. (6055)
...many of the warnings...
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c xrolo.index.c
...many of the warnings...
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c help.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c ctrlpanel.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c editor.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c listshell.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c dialog.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc: Optdriver: Bad optimizer option; ignored. (6055)
cc +O3 +OS -Wp,-H200000    -I/usr/include/X11R4/
-I/usr/include/Motif1.1 -DSYSV-DWIDGET_ACCESS -DMANUAL_CLIP
-c motif.c
cc: Optdriver: Bad optimizer option; ignored. (6055)
if [ -f xrolodex ]; then rm -f xrolodex~; mv -f xrolodex
xrolodex~; fi
cc -o xrolodex xrolo.o xrolo.db.o xrolo.index.o help.o streamdb.o
ctrlpanel.o editor.o listshell.o dialog.o strstr.o motif.o +O3
+OS -Wp,-H200000  -L/usr/lib/X11R4  -L/usr/lib/Motif1.1  -lXt
-lXext -lX11  -lPW
/bin/ld: Unsatisfied symbols:
   _XmSadjustLast (data)
   ...many listings...
 XmTextReplace (code)
 XmStringCreateSimple (code)
XmStringCreateLtoR (code)
	gmake: *** [xrolodex] Error 1
	40.70u 5.80s 1:50.15 42.2%
	ctshp>

I'm sure I'm missing something right in front of my nose...could
kind person point that out? :-) Thanks much.

David

-- 
============================================================================
David Doll                       UUNET: ..uunet!ctsx.celtech.com!davidd
Cellular Technical Services      Seattle, WA 98121             
2401 4th Ave., Suite 808         (206) 727-6372
From: robf@praxis.co.uk (Rob French)
Newsgroups: comp.windows.x.motif
Subject: What is Interface Architect?
Date: 21 Dec 92 13:30:18 GMT
Organization: Praxis, Bath, U.K.

Hi there

I'm sorry if this is the wrong news group.

I would be grateful for *any* information on Interface Architect.

Please E-mail your responses to robf@praxis.co.uk

TIA


Rob French
Newsgroups: comp.windows.x.motif
From: enertec@netcom.com (The Gang at Enertec)
Subject: real-time X/Motif data display user interface tool
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Wed, 23 Dec 1992 15:25:36 GMT


We are looking for a Unix / X / Motif product for the 486 platform
that provides a GUI interface for the definition and display of real time
data, including the ability to produce "trend" displays for the data.

Products that we have looked at include: FactoryLink from US DATA (under SCO)
and GE Cimplitity (under ISC).  Both of these products contain the ability to
draw graphical displays, then attach real-time data elements to those displays
in order change the color, size or values shown on those displays at run-time.

We are looking for a product that will do these things, PLUS provide us the
ability to build X/Motif applications (ala ISC's BuilderXcessory or UIM/X)
that will interact with the user and have the same look-and-feel as the windows
produced by the display generation tool.

If anyone has seen others products on the market that provide this or similar
capability, please drop us a line.  We'll post a summary of responses if anyone
else is interested.

Thanx in advance,

John Feras

enertec@netcom.com


-- 
enertec@netcom.COM
Netcom - Online Communication Services San Jose, CA
Newsgroups: comp.windows.x.motif
From: janzen@lichen.mpr.ca (Martin Janzen)
Subject: Re: access C++ non-static member data in callback functions
Reply-To: janzen@mprgate.mpr.ca
Organization: MPR Teltech Ltd.
Date: Tue, 22 Dec 92 21:04:43 GMT

In article <gregc.724963206@eagle.fsl.noaa.gov>, gregc@eagle.fsl.noaa.gov (Greg Compestine) writes:
>jng@aslslc71.asl.dl.nec.com (James Ng) writes:
>>[re. using Motif with C++]
>[...]
>The problem with using a non-static member function is
>that it has a hidden first parameter: the "this" ptr.  The X intrinsics
>callback dispatching routines have no provision for supplying the "this"
>ptr to the callback.
>
>   Doug Young discusses this problem and presents a workaround in his
>book "Object Oriented Programming with C++ and Motif".  Basically, you
>provide the "this" ptr as the client data to the static callback.  The
>static callback in turn calls the object's actual callback.  The tactic
>works fine until you hit the case of wanting to have such things as
>action procedures associated with your objects and *no* client data
>is available....

For Motif widgets, if you need the "this" pointer in an action procedure,
you can store it in the XmNuserData resource of any widgets for which the
action might be invoked.  All widgets that are subclasses of Primitive or
Manager (just about anything but shells) have this resource. Works for me...

-- 
Martin Janzen                     janzen@mprgate.mpr.ca (134.87.131.13)
MPR Teltech Ltd.                  Phone: (604) 293-5309
8999 Nelson Way                   Fax: (604) 293-6100
Burnaby, BC, CANADA  V5A 4B5
From: jsheng@PICA.ARMY.MIL ("Joseph Y. Sheng", IMD-PB)
Newsgroups: comp.windows.x.motif
Subject: Re:  Error: Shell Widget 3 has zero width ...
Date: 23 Dec 92 15:36:45 GMT
Distribution: inet
Organization: The Internet


  I am new to Motif, too.  I noticed that you set the arguments but you never
really implement those changes to the toplevel shell widget.  It should work
if you make the following change.

>>  XtSetArg(args[n], XmNwidth, 200); n++;
>>  XtSetArg(args[n], XmNheight, 200); n++;

    XtSetValues(toplevel,args,n);

>>  BULLETINBD_0 = XmCreateBulletinBoardDialog(toplevel,"BULLETINBD_0",args,n);

...Joe Sheng
   US ARMY
From: Deepak.Narain@cs.WPI.EDU (Deepak Narain)
Newsgroups: comp.windows.x.motif
Subject: Does a forked proc need something special to do Motif stuff?
Date: 30 Dec 1992 20:50:18 GMT
Organization: Department of Computer Science, WPI
Distribution: world
NNTP-Posting-Host: ivy.wpi.edu
Originator: dxn@ivy

I am writing a motif application that forks off a child process
(an xterm).  My problem is that the forked off process does not
display my widget - a MessageDialog.  What I do to get around 
the problem is trap SIGCLD, and display the widget from the parent
process, but, this is not what I want to do.  Has anybody ever run
into this problem before?  

This is the piece of code that I use to do the display from the child
(i.e, without setting up the signal stuff).

/* start here */
....

char *command = "/usr/bin/X11/xterm -e /usr/ucb/vi"
char *confirm[] = {"Confirm", "", ""};

int forked_pid = fork();

switch(forked_pid)
{
   case(-1):
      DisplayError("Fork Failed");
      return;

   case (0):
      system(command);
      DisplayHelp(confirm);
      exit(0)

   default:
      return;
      break;
}

...
/* end here */

The DisplayHelp is taken from the Young book, with a few minor mods, 
it works in all other cases, so I don't think that the problem is 
with that.  This is the error that I have been getting:

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Minor opcode of failed request:  0
  Resource id in failed request:  0xb0004c
  Serial number of failed request:  625
  Current serial number in output stream:  499
X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Minor opcode of failed request:  0
  Resource id in failed request:  0xb0004c
  Serial number of failed request:  621
  Current serial number in output stream:  612


Help...please.

Thanks,

------------------------------------------------------------------------
Deepak Narain                                   Deepak.Narain@cs.wpi.edu
From: jem@tinton.ccur.com (Jem Treadwell)
Newsgroups: comp.windows.x.motif
Subject: Re: How to change a window title dynamically ?
Date: 21 Dec 92 13:46:05 GMT
Distribution: inet
Organization: The Internet

Alain,

> I am looking for the way to change the title of a Shell Widget once it has
> been managed. This doesn't work at all :

> XtSetArg(args[0], XmNtitle, xs);
> XtSetValues(ShellWin, args, 1);

> Is something missing ???

Try doing it to XtParent(ShellWin).

Jem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jem Treadwell - jem@tinton.ccur.com

Mailstop 308,  Concurrent Computer Corporation,
2 Crescent Place, Oceanport, N.J. 07757
Phone: (908) 870 4798
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: comp.windows.x.motif
From: mep@reatta.camb.inmet.com (Mark Polhamus)
Subject: ValueChangedCallback & event (Text)
Summary: event not set on paste
Keywords: Text XmTextVerifyCallbackStruct ValueChangedCallback
Organization: Intermetrics Inc.
Date: Wed, 23 Dec 1992 16:26:57 GMT

I need to know when a user has modified a text widget, so I use a
ValueChangedCallback (reason XmCR_VALUE_CHANGED).  If the
XmTextVerifyCallbackStruct's event field is NULL, I assume that the
change did not occur because of the user's action, but because my
program called XmTextSetString().

This works in most cases, but I've found that the event field is NULL
when the user pastes into the text widget.

Is this a bug?  It happens on both sun4 and HP, Motif 1.1.  I would be
interested in pointers to bug reports - or a specification that agrees
with the current implementation.

I really wish this worked - I'll have to write some ugly hacks to work
around it.


-- Mark Polhamus
-- Intermetrics, Inc.
-- mep@inmet.inmet.com
From: janzen@lichen.mpr.ca (Martin Janzen)
Newsgroups: comp.windows.x.motif
Subject: Re: Any ideas for a Thermometer widget
Date: 22 Dec 92 21:24:52 GMT
Reply-To: janzen@mprgate.mpr.ca
Organization: MPR Teltech Ltd.

In article <Monica_Lee-221292085607@129.193.144.127>, Monica_Lee@smtp.esl.com (Monica Lee) writes:
>I want to create a thermometer widget.  I have the following ideas:
>
>1) use the drawing area widget
>2) use the scroll bar widget - if I can turnoff the directional arrows

This would certainly be the simplest approach.  All you need to do is:

  XtVaSetValues(scrollbar_widget, XmNshowArrows, False, NULL);

>3) maybe use the scale widget


-- 
Martin Janzen                     janzen@mprgate.mpr.ca (134.87.131.13)
MPR Teltech Ltd.                  Phone: (604) 293-5309
8999 Nelson Way                   Fax: (604) 293-6100
Burnaby, BC, CANADA  V5A 4B5
Newsgroups: comp.windows.x.motif
From: daniel@juliet.osf.org (Daniel Dardailler)
Subject: Re: Q: ScrolledWidndow with just vertical scrolling
Organization: Open Software Foundation, Motif Team
Date: Mon, 21 Dec 1992 15:07:58 GMT

  
|> I'm trying to create a scrolledWindow which has a rowColumn widget for what
|> it's viewing.  I'd like the rowColumn to be constrained so that its right
|> and left attachments are the scrolled window --- ie. I'd like the scrolled
|> window only to have a vertical scrollBar.  This way if the user resizes the
|> window's width, the things in my rowColumn will get wider (not display
|> more).
 
Mixed AUTOMATIC/APPLICATION_DEFINED scrollingPolicy is not supported
in the scrolled window today.

The best I can suggest is AUTOMATIC with the application tracking the
resize event on the scrolled window and resizing the rowcolumn so that
the horizontal scrollbar is never shown.

Newsgroups: comp.windows.x.motif
From: daniel@juliet.osf.org (Daniel Dardailler)
Subject: Re: Help: Resizing widgets
Organization: Open Software Foundation, Motif Team
Date: Wed, 23 Dec 1992 15:28:50 GMT

 
|> A have a form widget manage with the main window as the parent.  When I
|> maximise the main window, the form remain the same size.  What should I do
|> to so that the form widget will resize with the parent.
|> 

A guess: don't use AUTOMATIC mode for the SW.


|> In the FileSectionBox, how can I restrict the section box to only show the
|> file names instead of showing the full path.  
|> 
 
What version of Motif are you using ?
That should be the default since 1.1.
Newsgroups: comp.windows.x.motif
From: daniel@juliet.osf.org (Daniel Dardailler)
Subject: Re: HELP: How to "fake" button events in a scrollbar widget?
Keywords: motif, scrollbar, events
 
Organization: Open Software Foundation, Motif Team
Date: Mon, 21 Dec 1992 15:10:35 GMT

|> How can I invoke the appropriate Motif callback for a scroll bar as if the user
|> has selected page up or page down on a scroll bar.  I have a scrolled window
|> with several text widget in it for user input.  A page up or page down scrolls
|> to the previous or next row of text widgets.  I need to be able to display the
 
Use XmScrollBarSetValues with page increment after you go the 
scrollbar id and the page increment using XtGetValues.
From: jburnes@csisun.uucp (Jim Burnes)
Subject: Where can I get MOTIF?
Organization: CompuSci, Inc
Date: Thu, 31 Dec 1992 16:59:51 GMT

I would like to use MOTIF as a window manager for XFree86
on my 386bsd box.

What is the latest version?  Where can I get the sources
and how much will it set me back?


Thanks in advance...

Jim Burnes

Newsgroups: comp.windows.x.motif
From: koverber@cs.ulowell.edu (Kurt Overberg)
Subject: Re: How to change a window title dynamically ?
Originator: koverber@bigmax.ulowell.edu
Organization: University of Massachusetts at Lowell Computer Science
Distribution: inet
Date: Thu, 24 Dec 1992 14:09:54 GMT


In article <9212201248.aa09927@brahms.tinton.ccur.com>, jem@tinton.ccur.com (Jem Treadwell) writes:
|> Alain,
|> 
|> > I am looking for the way to change the title of a Shell Widget once it has
|> > been managed. This doesn't work at all :
|> 
|> > XtSetArg(args[0], XmNtitle, xs);
|> > XtSetValues(ShellWin, args, 1);
|> 
|> > Is something missing ???

I believe that you don't use an XmString as a parameter, 
you use a regular string.  Could'nt tell from you code
segment which you used...


				peace out.

					 kurt
-- 
Kurt Overberg            | I honestly doubt you care about my opinions ;^)      
U of Mass, Lowell        | "Poke a double-decker on a Llama taboot,       
koverber@cs.ulowell.edu  |  Llama taboot, taboot!"      -Phish
From: fkmunker@cip.informatik.uni-erlangen.de (Frank Munkert)
Newsgroups: comp.windows.x.motif
Subject: Application shell position
Date: Wed, 30 Dec 1992 10:31:05 GMT
Organization: CSD., University of Erlangen
Distribution: inet
NNTP-Posting-Host: faui00a.informatik.uni-erlangen.de
Keywords: Motif

Hi,

I have encountered the following problem with the Motif Window Manager
(mwm):

If I specify the position of an application in the resource file as 

     Application.x: 50
     Application.y: 50

the application shell will not appear at position (50, 50) but
somewhere else. Actually, mwm will select a new position for
the application each time the application is invoked. This
behaviour of mwm is very confusing for the user of the application,
who expects the application window to appear always at the same
place.

This problem will not occur if I use the Open Look Window Manager
(olwm) instead.

Is there any way to force mwm to display an application shell window
at a determined position (except from the -geometry option)???

Happy new year to everybody!

   Frank (fkmunker@cip.informatik.uni-erlangen.de)

---
Frank Munkert            |  Uni Erlangen
Zum Froschbruecklein 5   |  
8500 Nuernberg 10        |  <fkmunker@cip.informatik.uni-erlangen.de>
Germany                  |  or: <fmu@pki-nbg.philips.de>
Newsgroups: comp.windows.x.motif
From: stevep@twisto.compaq.com (Steve Pearlmutter)
Subject: Re: PushButton behavior
Organization: Compaq Computer Corporation, Houston, TX.
	<3948@creatures.cs.vt.edu>
Distribution: world,local
Date: Wed, 23 Dec 1992 14:21:07 GMT

>>>>> On 22 Dec 92 23:38:56 GMT, ramakris@csgrad.cs.vt.edu (S.Ramakrishnan) said:

> In article <1992Dec21.144630.10264@osf.org> daniel@juliet.osf.org (Daniel Dardailler) writes:

>    Someone@inet.d48.lilly.com queries...

>   >|> I would like to have my pushbuttons behave the same way pushbuttons do
>   >|> in dialogs (e.g. fileselectionbox) when the keyboardFocusPolicy is set
>   >|> to true.  In dialogs, when pushbuttons take focus they show as default.
>   >|> But for the pushbuttons I create, I can only make them show a border
>   >|> around the pushbutton (by setting highlightOnEnter to true).

> >Default button behavior is a trait of the BulletinBoard widget.
> >Look there in the doc.

> Yes, but that was not the question. Bulletinboard will call the "activateCallback" callback
> of the pushbutton whih has been set as its (BB's) "defaultButton". But the problem is to
> show the defaultButton the way the default buttons appear on a XmSelectionBox: with
> a large border around the button.

> I have tried setting the "shadowThickness" of the XmPushButton child of the
> bulletinboard to 5 and have set the pushbutton as the defaultButton of the BB.
> Yet, the button doesn't look as the way defaultButtons do on a XmSelectionBox.

> This is an irritant when you are trying to construct your own dialog. They look
> different from the "readymade" dialogs because of the buttons.


> Ps: Is "borderThickness" the answer ? Should on set the "borderThickness" of the
>     window of the "defaultButton" also to a high value, apart from "shadowThickness" ?
>     Yuck !

I believe you are are looking for the showAsDefault resource on the PushButton.

--
Steve Pearlmutter                        | Nothing I say in any way  
stevep@twisto.compaq.com                 | represents the opinions of
Compaq Computer Corporation, Houston, TX | my employers.  Really.
"Good taste is timeless... and a good time is usually tasteless."

Newsgroups: comp.windows.x.motif
From: edbis@solomon.technet.sg (Koh Eng San)
Subject: Help: Resizing widgets
X-Newsreader: TIN [version 1.1 PL8]
Date: Wed, 23 Dec 1992 09:54:59 GMT

I'm a new Motif programmer and could anybody enlighten me on the following:

A have a form widget manage with the main window as the parent.  When I
maximise the main window, the form remain the same size.  What should I do
to so that the form widget will resize with the parent.

In the FileSectionBox, how can I restrict the section box to only show the
file names instead of showing the full path.  

Welcome any help render ....


Thanks in advance ...... Merry X'mas



--
===============================================================================
Koh Eng San				Tel: (65) 3306-779
Systems Programmer			Fax: (65) 3306-786
Economic Development Board		Internet Id: edbis@solomon.technet.sg
of Singapore

			Have a GREAT Day!!!
==============================================================================
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x.motif
Subject: Re: Seeking Motif style guide checklist
Date: 30 Dec 1992 21:28:48 GMT
Organization: DEC Western Software Laboratory
Distribution: world
Reply-To: klee@wsl.dec.com
NNTP-Posting-Host: alhambra.pa.dec.com

In article <1992Dec17.200404.21849@pencom.com>, windy@pencom.com (Windflower Gilbert) writes:
|> Has anyone ever created a checklist for Motif Style Guide conformance? I  
|> could really use one.

Appendix B of the Prentice-Hall book *OSF/Motif Style Guide (Release
1.2)* is titled "OSF/Motif Level One Certification Checklist".  This is
probably what you want.

-- 
Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee
Newsgroups: comp.windows.x.motif
From: garath@irony.engin.umich.edu (Scott Grosch)
Subject: Drag and Drop example
Date: Tue, 29 Dec 92 08:21:46 EST
Organization: University of Michigan (CAEN)
Reply-To: garath@engin.umich.edu
Originator: garath@irony.engin.umich.edu


Would someone be willing to send me a small example of how to use the drag and
drop routines in motif 1.2?  I don't understand atoms at all, so I'm totally
lost with what to do.  

I have a RowColumn widget that I want to be the source, and I have a label
widget (an XpmPixmap basically) that I want as the drop site.  When the icon
moves over the label widget I'd like for the icon to change to another icon
so that the person knows they can drop there, but this is not at all necessary.
Thank you very much.

		--Scott


-- 
Scott Grosch                              Internet: garath@engin.umich.edu
Programmer                                        Bitnet: user7a4b@umichum
Computer Aided Engineering Network                  University of Michigan