HDTenEightyP/NetNews huggingface dataset:
From: karl@rss.dl.nec.com (Karl Larson)
Subject: XmAddTabGroup
Keywords: why not?
Organization: NEC America
Date: Thu, 10 Sep 1992 15:15:20 GMT

The Motif Programming Manual Version 1.1 by O'Reilly & Associates (pages 283-284) states "To maintain backward compatibility, whenever XmTabGroup() is
called, the toolkit assumes the programmer is using the old Motif 1.0 specifications and disables the new, automatic behavior".  It goes on to state
"Calling XmAddTabGroup() is equivalent to setting XmNnavigationType to XmEXCLUSIVE_TAB_GROUP" and recommends against using XmAddTabGroup().


I have several questions concerning this:

1) What is the recommended way of ordering widgets other than the normal "Left to Right and then Top to Bottom" order of a constraint widged?  I could process the traversal event manually, but this seems like the long way to do this.

2) If the XmNnavigationType is set to XmEXCLUSIVE_TAB_GROUP, then my interpretation of the text is that tab groups are not added automatically (as in Motif 1.0) and therefore a TAB should not be possible.  When I added added "*navigationType:  XmEXCLUSIVE_TAB_GROUP" to my .Xdefaults file, I was still able to TAB.  Also, it seemed to produce undesired affects on traversal in general.  Selecting on a PushButton whose traversalOn was set to False had the
same effect as using the TAB key.  Does anyone have any ideas why?

3) Where can I get more information on this subject.  The most that I've seen is about 6 pages.


Summary:
I am tring to use a "Top to Bottom and then Left to Right" order inside a single constraint widget.  This was rather simple by setting the traversalOn to False
for all widgets and then manually adding them using the XmAddTabGroup().  My problem is that selecting a pushbutton inside of the constaint widget performs
a TAB also. 


Thanks

Karl Larson 
work (214)-907-4463
home (214)-328-2563
From: jefft@athena.mit.edu (Jeff Tang)
Newsgroups: comp.windows.x.motif
Subject: I need to set the font list for a form widget
Date: 14 Sep 92 16:30:38 GMT
Article-I.D.: hydrox-c.JEFFT.92Sep14123005
Distribution: comp
Organization: Massachusetts Institute of Technology


I'm porting an application to some AIX3.2 RS/6000's.  It worked find on
AIX3.1, but now I'm getting:

Warning:
    Name: mainForm
    Class: XmForm
    Null font list (no vendor shell default)

for my form widgets and it's dumping core when I do a:
XtCreateManagedWidget to create a form widget instead of an XmCreateForm, I
get a segmentation violation.

Does anyone know what I need to do to get this to work?

Thanks,
--
Jeff Tang
jefft@athena.mit.edu
From: dbrooks@osf.org
Newsgroups: comp.windows.x.motif
Subject: Re:  I need to set the font list for a form widget
Date: 14 Sep 92 23:47:03 GMT
Distribution: inet
Organization: The Internet

jefft@athena.mit.edu  (Jeff Tang) writes:
	I'm porting an application to some AIX3.2 RS/6000's.  It worked find on
	AIX3.1, but now I'm getting:
	
	Warning:
	    Name: mainForm
	    Class: XmForm
	    Null font list (no vendor shell default)

It's possible that you have switched to using a shared libXt from an
unshared.  Doing this on AIX requires serious magic in the way you build a
widget library.  Xaw demonstrates the details.

David Brooks
OSF
From: ksivasam@ha02.eng.ua.edu (Kalidoss Sivasamy)
Newsgroups: comp.windows.x.motif
Subject: (none)
Date: 8 Sep 1992 14:45:17 -0500
Organization: UTexas Mail-to-News Gateway
Distribution: inet
NNTP-Posting-Host: cs.utexas.edu




Motif pros please ignore this..


I have some tutorial files from "Brian" for 
Motif beginners. If somebody needs these files,
send me a mail. I found fairly simple examples
for different applications. Hope this would help
the beginners..

Kalidoss.

my e-mail : ksivasam@ha02.eng.ua.edu
From: andy@autodesk.com (Andrew Purshottam)
Newsgroups: comp.windows.x.motif
Subject: Re: JOB OPPORTUNITIES POSTINGS
Date: 11 Sep 92 18:51:34 GMT
Distribution: inet
Organization: The Internet

The Motif Developer's Group and Drinking Soc. has started a job bank.
Perhaps that would be the appropriate way to deal with postings. 
I do not have the job back blurb handy. Would someone please post the job bank
mailing addresses?
-
Andrew V. Purshottam      /\     |  andy@autodesk.com  ...!fernwood!acad!andy 
Autodesk, Inc.	         //\\    |  (415)332-2344x2161  FAX (415) 331-8093
2320 Marinship Way      ///\\\   |  Sausalito CA 94965
"The views expressed are those of the speaker."
Newsgroups: comp.windows.x.motif
From: cecchinr@gehrig.cs.rpi.edu (Ron Cecchini)
Subject: Re: Is there something analogous to XtIsMapped() ?
Organization: Rensselaer Polytechnic Institute, Troy, NY
Date: Thu, 10 Sep 1992 14:36:45 GMT

In article <DRAND.92Sep9181726@spinner.osf.org> drand@spinner.osf.org (Douglas Rand) writes:
>In article <7a5yxra@rpi.edu> cecchinr@hornsby.cs.rpi.edu (Ron Cecchini) writes:
>
>     There is XtIsManaged() and XtIsRealized().  I need XtIsMapped() and
>   there is none.  What is the easiest way to detect this (I'm not
>   having any luck trying to use the widget's resources).
>
>Why do you care?  You need to know XtIsRealized so you don't draw
>to a NULL window,  but why do you need the mapping state?  You 
>normally draw to a Widget's window in response to an Exposure.
>The server won't generate these events until the window is mapped.
>
>
>
>--
>Douglas S. Rand <drand@osf.org>		OSF/Motif Dev.
>Snail:         11 Cambridge Center,  Cambridge,  MA  02142
>Disclaimer:    I don't know if OSF agrees with me... let's vote on it.
>Amateur Radio: KC1KJ

Right, but I *still* want to know when a widget has been mapped or not.
It may be managed, and I may be doing things with it, but I want to be able
to tell when the widget has been mapped.  I don't think its a completely
weird thing to do...

Ron

p.s. I've already received a couple of solutions to this question,
     so I guess no one else has to respond.  You can if you want, though...

     But I think I'd appreciate it more if someone could figure out the
     problem I was having with SelectionBoxes and multiple fonts...
From: yngvi@rhi.hi.is (Yngvi Sigurjonsson)
Newsgroups: comp.windows.x.motif
Subject: Viewing large text (browser?) with motif.
Summary: Need to view large texts in motif
Keywords: large text
Date: 16 Sep 92 00:44:04 GMT


We have a text buffer generated in memory that we need to be able
to browse through.  The problem is that this text can be anywhere
from few K's in size upto several megabytes.

When we throwed this into a XmText widget for viewing we tried to
set in advance the maxLength resource to 1 Mb (otherwise there
was a cut off size around 32K). We checked how much memory the 
program used, and as far as we could see it used 3Mb to store a
1Mb file!  Any ideas?

Has anyone found a way around this or maybe even implemented a browser
for large text files.  We can easily, if needed, dump this text to a 
text file for browsing which might be a better solution anyway.  

Thanks in advance,

Bjarni & Yngvi


--
 /| Yngvi Thor Sigurjonsson         |\ |\ ______________________/|
| | Fljotasel 17                    | || |   yngvi@rhi.hi.is   | |
| | Reykjavik Iceland               | || |_____________________| |
 \|_________________________________|/ |/_______________________\|
Newsgroups: comp.windows.x.motif,comp.windows.x
From: scott@asd.com (Scott Barman)
Subject: Mixing Motif and Athena widgets?
Organization: American Software Development Corp., West Babylon, NY
Date: Thu, 3 Sep 1992 18:13:26 GMT

In an application, the Athena asciiDiskWidget seems to be the perfect
solution to a problem, but the program is written using Motif (1.1.5). 
Can I "safely" use the an asciiDiskWidget in a Motif program?  Or is
there some way of doing the same thing in Motif?

Thanks!
-- 
scott barman			| <This space intentionally left blank>
scott@asd.com			|
 (I can barely speak for myself, you expect me to speak for my employer??)
Newsgroups: comp.windows.x.motif
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
Subject: WM_SAVE_YOURSELF issues
Organization: Jet Propulsion Lab, Pasadena, CA
Date: Tue, 15 Sep 92 21:26:59 GMT


I'm finally getting around to addressing some session management issues 
in our programs and would like to design a solution that will work with
1.2 too, if and when we ever get our 1.2 license straightened out.

In 1.1.4, if a client registers for both WM_DELETE_WINDOW and WM_SAVE_-
YOURSELF, mwm sends WM_DELETE_WINDOW first, then sets a timer, sends 
WM_SAVE_YOURSELF, and watches for a change of the WM_COMMAND property.  
When the WM_COMMAND property changes, the window is then destroyed via 
XKillClient.  And, if the timer expires before the WM_COMMAND property 
is set, then the window is destroyed via XKillClient.  

(What *wasn't* immediately obvious from *any* documentation, was that I 
had to set XmNdeleteResponse to XmDO_NOTHING on my top level shell so that 
the VendorShell wouldn't pre-emptively destroy the program application 
context before the WM_SAVE_YOURSELF message was delivered.  If you're 
listening, Dan, O'Reilly Vol. 6 is seriously deficient in this regard -- 
your sample program has typos and those not withstanding, just doesn't 
work! The OSF/Prentice Hall documentation is deficient too, but to its 
credit, doesn't give flawed example programs.)

We're not using twm in this system, but I note that the R5 twm handles the 
delivery of these two messages (WM_DELETE_WINDOW and WM_SAVE_YOURSELF) as 
separate actions; triggered from separate entries on a twm menu.

Our "product" is only used internally on a "turn-key" system, and it's
unlikely that any other window manager than mwm will be used.  Never the
less, I'd like to be as portable as possible.  Does anyone have any caveats 
about session management issues under twm or olwm, especially as compared 
to mwm?

I was under the impression that OSF was following the evolution of the 
ICCCM, so that even though 1.1.x is nominally R4 based, it would operate 
correctly as defined by the ICCCM that was eventually released with R5.  
Given the apparent minor disparity between mwm and twm, it appears that 
I was mistaken; anyone care to comment?

I know that 1.2 advertises itself as "binary compatible" to 1.1.x.  Can I
anticipate that mwm behaviour in 1.2 is unchanged?  If the answer is no,
can someone enlighten me as to how 1.2 does work?  (We actually have the
source to 1.2, but only a single source license and no binaries, so I can't 
look for myself, nor can I try it and see. :-( )

-- 

Kaleb Keithley                          kaleb@thyme.jpl.nasa.gov

Not authorized, in any way, shape, or form, to speak for anyone.

Newsgroups: comp.windows.x.motif
From: cecchinr@dimaggio.cs.rpi.edu (Ron Cecchini)
Subject: SelectionBoxes and multiple fonts - 3rd DESPERATE attempt
Organization: Rensselaer Polytechnic Institute, Troy, NY
Distribution: inet
Date: Tue, 8 Sep 1992 20:55:05 GMT

Hi all,

  I still didn't get any responses to a question I had posted a
couple of times last week - so, I'm going to repost one of my original
messages:

----------


 I hope someone from OSF is reading this, because I can't find 
anything anywhere about this problem: 

I have a SelectionBox.  Some of the items in the SelectionBox's List 
widget child are in a bold font, and the rest are in the default font. 
Whenever I try to select an item that is in bold font, it doesn't 
get selected; i.e. it doesn't appear in the SelectionBox's
Text widget child. 
 
I realized earlier today that I wasn't loading the bold font
into the Text widget child (like I was doing for the List widget 
child) - so I did that, and *still* no dice. 
 
Please tell me that I don't have to implement my own SelectionBox!!!
 
Thanx,
Ron
From: dwd@cbnewsc.cb.att.com (David W. Dykstra)
Newsgroups: comp.windows.x.motif
Subject: Re: How to keep F10 from activating menubar?
Date: 9 Sep 92 14:50:26 GMT
Organization: AT&T

In article <1992Sep4.222553.8316@cbnewsc.cb.att.com> I asked how
to override the behavior of F10 activating a window's menu bar.
After further experimentation, it appears there's only one way to
do it: by specifying a different key combination for osfMenuBar
in the defaultVirtualBindings application resource.  (By the way,
note that defaultVirtualBindings is not a resource of any widget,
and must be specified in the resource database from an external
file or the command line, before XtInitialize() is called.)

I tried overriding the translation of the <Key>osfMenuBar event in
the widget of interest and every one of its ancestors, but that had
no effect.  It's almost as though osfMenuBar generates a different
kind of event than a plain <KeyPress>.  From the description of
accelerators in the O'Reilly manual, this seems like the mechanism
that should be used to implement the osfMenuBar function, but since
accelerators are just an extension of event translations, Motif must
be doing something else.

If anyone can explain the mechanism that's used any better, or show
another way to override it, I'd still be interested.

adTHANKSvance,
Jon Luers
ADDS/NCR/AT&T
jhl@qwerty.ih.att.com
From: billb@gdfwc3 (Bill Baumann)
Newsgroups: comp.windows.x.motif
Subject: Motif Training
Date: 10 Sep 92 20:43:22 GMT
Reply-To: baumann@gdwest.gd.com
Distribution: comp.windows.x.motif
Organization: General Dynamics, Fort Worth Division


I'm looking for Motif training.  Does anyone know of reputable companies
doing training in Dallas.  I'm hoping to find a class sometime this year.
(The only one I know of is offered March '93.)

Thanks for any help


Bill Baumann				Email     : baumann@gdwest.gd.com
General Dynamics			Telephone : (817)763-1176
--
						Bill Baumann (billb)
						texsun!gdfwc3!kuwait!billb
						tel. (817)777-0269
From: jrh@de.deere.com (John R. Howell)
Newsgroups: comp.windows.x.motif
Subject: nfs over X.25???
Date: 14 Sep 92 15:14:15 GMT
Followup-To: comp.windows.x.motif
Organization: Deere & Company

I know it is probably not a good idea from a performance standpoint, but is
it possible to run nfs (mount an nfs filesystem) over an x.25 connection.

I have heard that the "store and forward" technique that x.25 uses would
not be conducive to nfs, but I would be interested in learning more
specifics.

Thanks.

John Howell
Deere & Company
(The Big Green Tractor People)
jrh@de.deere.com
Newsgroups: comp.windows.x.motif
From: glenm@bnr.ca (Glen Martin)
Subject: Problem with scrollbar in ScrolledText
Reply-To: glenm@bnr.ca
Organization: Bell-Northern Research Ltd.
Date: Wed, 09 Sep 92 19:16:07 GMT

I'm having a problem moving the slider on a scrollbar via XtSetValues.
What I'm trying to accomplish is a non-user-editable text which
scrolls to the bottom whenever new lines are appended.

What happens is that something seems to be overriding my changes to
the 'value' of the scrollbar.

Here is the code I use to create stuff:

  nargs = 0;
  XtSetArg(args[nargs],XmNeditable, edit); nargs++;
  XtSetArg(args[nargs],XmNeditMode, XmMULTI_LINE_EDIT); nargs++;
  XtSetArg(args[nargs],XmNscrollingPolicy, XmAUTOMATIC ); nargs++;
  XtSetArg(args[nargs],XmNscrollBarDisplayPolicy,  XmAS_NEEDED ); nargs++;

  _text = XmCreateScrolledText( parent, name, args, nargs );
  _w = XtParent( _text );

  nargs = 0;
  XtSetArg(args[nargs],XmNverticalScrollBar,&_vScrollBar); nargs++;
  XtGetValues( _w, args, nargs );


and here is the code to append stuff to the text:

  // insert the text
  XmTextPosition tp = XmTextGetLastPosition(_text);
  XmTextInsert(_text,tp+1,s);

  // set scroll position
  int maximum, size, value;
  int nargs;
  Arg args[10];

  nargs = 0;
  XtSetArg(args[nargs],XmNmaximum,&maximum); nargs++;
  XtSetArg(args[nargs],XmNsliderSize,&size); nargs++;
  XtSetArg(args[nargs],XmNvalue,&value); nargs++;
  XtGetValues( _vScrollBar, args, nargs );

  cout << "Value at " << &value << " is " << value << endl;

  value = maximum - size ;

  nargs = 0;
  XtSetArg(args[nargs],XmNvalue,value); nargs++;
  XtSetValues( _vScrollBar, args, nargs );

  nargs = 0;
  XtSetArg(args[nargs],XmNvalue,&value); nargs++;
  XtGetValues( _vScrollBar, args, nargs );

  cout << "Value at " << &value << " is now " << value << endl;


Here is the output I get as I append one line at a time:

 Value at 0xffeffa08 is 0
 Value at 0xffeffa08 is now 1
 Value at 0xffeffa08 is 0
 Value at 0xffeffa08 is now 2
 Value at 0xffeffa08 is 0
 Value at 0xffeffa08 is now 3
 Value at 0xffeffa08 is 0
 Value at 0xffeffa08 is now 4
 Value at 0xffeffa08 is 0
 Value at 0xffeffa08 is now 5
 Value at 0xffeffa08 is 0
 Value at 0xffeffa08 is now 6

So, the value is being changed, but something is overriding it.
Apparently.

Now the problem may well be the scrolling policy of 'automatic',
but I had hoped that I could manually set a scroll point if I
wanted, leaving the library to deal with the users' maneuvers with
the scrollbar. Am I off in left field on this?

Feel free to respond via email, and I'll summarise replies here.

--------------------------------------------------------------------------------
Glen Martin              Bell-Northern Research          Ottawa, Ontario, Canada
Phone : (613) 763-7299   Fax: (613) 763-2626             Internet: glenm@bnr.ca
--------------------------------------------------------------------------------
From: costant@scsun2.CSELT.STET.IT (Gian Paolo Costantino - CSELT - Italy)
Newsgroups: comp.windows.x.motif
Subject: How to make popup widgets automatically placed
Date: 8 Sep 92 15:42:42 GMT
Distribution: inet
Organization: The Internet

Hi Motif world,
I have an apparently simple problem I couldn't solve.
I'm using UIM/X on HP-UX 8.0.
My application has to display several popup widgets (Dialogs and non-Dialogs)
I desire been placed automatically in some place (the best is centered on
the parent). I have tried using the Resource XmNdefaultPosition = True when
it was possible but it seems it doesn't work.
When the widgets are managed the user must always place them manually.
If I set the "interactivePlacement" to False for my mwm it is the Window
Manager that places the widgets in a way I don't like at all.
How can I force the automatical positioning of my widgets?

Thank you in advance.

************************************************************************
*               Gian Paolo Costantino                                  *
*               CSELT  -  Turin  -  Italy                              *
*               costant@scsun2.cselt.stet.it                           *
************************************************************************
Newsgroups: comp.windows.x.motif
From: vamsee@cs.tamu.edu (Vamsee Lakamsani)
Subject: fallback resources, fails to link
Organization: Computer Science Department, Texas A&M University
Distribution: usa
Date: Fri, 11 Sep 1992 17:08:37 GMT

Hi,

I have a problem with fallback resources. It fails while linking.
the error I got is,

###########################
ld: buildmenu.o: _fallbacks: multiply defined
collect: /usr/bin/ld returned 2 exit status
*** Error code 1
########################

I have defined fallbacks as type String as given is Dan Heller's book.
Also what exactly does this " multiply defined" mean. It raises its
ugly head quite frequently here.

"uname -a" on this workstation gave : SunOS sparc48 4.1.1 4 sun4c
The version of Motif here is 1.1.1.

Please send your suggestions by  E-mail to vamsee@tamu.edu

Thanks
vamsee
From: billb@gdfwc3 (Bill Baumann)
Newsgroups: comp.windows.x.motif
Subject: Motif Training
Date: 10 Sep 92 20:42:57 GMT
Reply-To: baumann@gdwest.gd.com
Distribution: comp.windows.x.motif
Organization: General Dynamics, Fort Worth Division


I'm looking for Motif training.  Does anyone know of reputable companies
doing training in Dallas.  I'm hoping to find a class sometime this year.
(The only one I know of is offered in March '93.)

Thanks for any help


Bill Baumann				Email     : baumann@gdwest.gd.com
General Dynamics			Telephone : (817)763-1176
--
						Bill Baumann (billb)
						texsun!gdfwc3!kuwait!billb
						tel. (817)777-0269
From: al@osf.org (Alastair Gourlay)
Newsgroups: comp.windows.x.motif
Subject: Re: How to make buttons look pressed in ??
Date: 11 Sep 92 13:33:53 GMT
Distribution: inet
Organization: The Internet


> I would like to have two push buttons and have them act like a 
> radio box, where you push one button in and the other "pop" out.
> Also when you push the button in I would like to have it look as 
> though it is still pressed in.  I anybody has done this, or seen 
> it done

You could try something like this (transcribed into the widget creation
language of your own choosing):

object rb : XmRadioBox {
    arguments { };
    controls {
	XmToggleButton tb1;
	XmToggleButton tb2;
    };
};
object tb1 : XmToggleButton {
    arguments {
	XmNindicatorOn = false;
	XmNfillOnSelect = true;
	XmNshadowThickness = 2;
	XmNlabelString = "Bold";
    };
};
object tb1 : XmToggleButton {
    arguments {
	XmNindicatorOn = false;
	XmNfillOnSelect = true;
	XmNshadowThickness = 2;
	XmNlabelString = "Italic";
    };
};

The toggle buttons will appear raised when unset, and pressed in when set.
You'll get radio behavior for free.

In 1.1 the background of a set button will be the same as that of an unset
button. In 1.2, if XmNfillOnSelect is true, a set button will have its
background filled with XmNselectColor.


	Alastair Gourlay.
Newsgroups: comp.windows.x.motif
From: dpunjabi@nyx.cs.du.edu (DINESH PUNJABI)
Subject: Where should I generally define Widgets ( local, global, etc )
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Mon, 14 Sep 92 23:09:09 GMT

I am new to this newsgroup and to motif for that matter. What is a good
style for declaring Widgets. I mean, should I define Widgets as globals
or static locals, etc. This is not a problem for small self-contained 
programs, but I am getting involved in an  application that could make use
of a very large number of widgets. I frequently reference widgets within
callbacks and would appreciate any coding style related EMAIL feedback
about this issue.


Rgds

Dinesh
--

Dinesh Punjabi 
dpunjabi@nyx.cs.du.edu                Work: (303)-595-2901
Newsgroups: comp.windows.x.motif
From: gerth@PrakInf.TH-Ilmenau.DE (Gerth)
Subject: position of the work area in a dialog
Reply-To: gerth@PrakInf.TH-Ilmenau.DE (Gerth)
Organization: Technische Hochschule Ilmenau
Date: Sun, 13 Sep 92 09:17:28 GMT

Hi,

I have got a problem with the right positioning of the work area widget
in a dialog widget (in my case a SelectionBox). 
I unmanaged the list, text and text label widgets and then created a 
RadioBox as a child of the SelectionBox. This works well fine but the 
RadioBox doesn't appear straight below the list label how I expected 
and wanted it to be.
I tried to set the XmNy resource of the RadioBox but the SelectionBox
rejects all requests and forces the y position to have the value 138.

Any suggestions how I can control the position of the RadioBox?

Thanks in advance.

Thomas Gerth
gerth@prakinf.th-ilmenau.de
Technical University of Ilmenau, Germany
From: rct@fulcrum.bt.co.uk (Richard Taylor)
Newsgroups: comp.windows.x.motif
Subject: Multi-colour List Widgets
Date: 8 Sep 92 15:40:06 GMT
Organization: Fulcrum Communications

Multi-colour List Widgets
-------------------------

I need to have a list of differently coloured text items, which can be
selected. This cannot be done in a normal Motif List widget, but about a
month ago there was a lot of network traffic on the subject. Naturally, I
wasn't interested then, but I am now!

Did anyone keep any of the useful replies as to how to do this?
I would appreciate if it was sent by email rather than to the net, as I dont'
often read .motif.

Thanks in advance,

============================================================================
Richard Taylor                 DoD #981               (rct@fulcrum.bt.co.uk)
"Gentlemen, starta your engines... 2 minutes, to the hills." Massimo Laverda
============================================================================
Fulcrum Communications Ltd., Fordrough Lane, Birmingham, B9 5LD, ENGLAND.