HDTenEightyP/NetNews huggingface dataset:
From: faedi@loria.fr (Faedi Joel)
Newsgroups: comp.windows.x.motif
Subject: Alarm and screen-saver
Date: 11 Jan 93 11:55:24 GMT
Organization: CRIN (CNRS) Nancy - INRIA Lorraine

Hello,

I'm writing a program under X11R4 and Motif.
It must raise alarms on the X terminal. But there is a problem
when the screen saver is on : my red blinking alarm window can
never be seen ! 

A friend told me that there was a solution here about a year ago.
Could anybody help me ?

Tanks in advance

------------------------------------------------------------------------
Faedi Joel                                        faedi@isial.u-nancy.fr
                                                  faedi@loria.fr
Newsgroups: comp.windows.x.motif,comp.windows.x,comp.windows.open-look
From: khuhner@eng.auburn.edu (Kurt E. Huhner)
Subject: Re: XAPPLRESDIR
Organization: Auburn University Engineering
Date: Fri, 8 Jan 1993 15:46:53 GMT

In article <1355@pivot-sts.sbi.com> ray@rann.sbi.com writes:
>Hi All
>  I'm trying to get my resource file via the XAPPLRESDIR environment variable and am not having much luck. Based on info in the OSF/Motif programmer's guide, I believe that I can use this var as follows
>  "setenv XAPPLRESDIR = $APPLHOME/etc"
>register my appl class as "XTimesheet"
>  and then put my defaults file in...
>  "$APPLHOME/etc/XTimesheet"
> and the user can override these defaults by putting THEIR preferences in
>  "~/XTimesheet"
>I can't get this to work (!!!%@$!%^@) (BTW -The LANG var is not set). Can anyone either explain or point me to the proper usage. I'm currently using $XENVIRONMENT to point to me defaults but that doesn't let the user override easily.

   Set the XAPPLRESDIR to ./  This says look in the current directory BUT the
current directory must be the SAME NAME as the application!!

>  Thanks
>---Raymond
From: lmpieni@afterlife.ncsc.mil (Lori M. Pieniazek)
Newsgroups: comp.windows.x.motif
Subject: getting widgets to re-read resource database
Date: 11 Jan 93 14:31:18 GMT
Organization: The Great Beyond

This is a follow up question to a question I posted (about a week ago)
about dynamically changing the background resource value.

I have an application that reads in resources from a file and sets widgets
up accordingly. While the application is running I want to be able to
change a resource value and have all of the widgets change accordingly.
I am able to change the resource value by adding it to
the resource database using the following XrmPutLineResource call. Any of
the resources that I add before I create the widgets take effect, however, after
the widgets have been created and managed, another call to XrmPutLineResouce
has no effect. 

The problem is that I do not know how to make the widgets re-read their 
resources from the resouce database that has been just changed, thus, 
changing their background color. I have tried to unmanage/manage but 
that does not seem to work.  

If there is a better way or different way of achieving the same results please
let me know. I am looking for a way to change all of the widgets after they
have been created and managed without having to specifically set the value 
of the background individually for all the widgets.


resource file:
*background:	red

application:

database = XtDatabase(XtDisplay(shell));
.
.
.
.
XrmPutLineResource (&database,"*background: greeen");



Thanks in advance!

Lori Pieniazek
lmpieni@afterlife.ncsc.mil
Newsgroups: comp.windows.x.motif
From: simon@guk.auspost.com.au (Simon Carter)
Subject: XmTextField.maxLength problem
Organization: Australia Post
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 8 Jan 1993 04:37:54 GMT


Under Motif 1.1.4, setting the maxLength of a text field does not prevent
XtVaSetValues from inserting a string *longer* than maxLength.

When this occurs, no editing is possible, particularly deleting single
characters, although deleting a block of text that will cause the field
to be <= MaxLength does actually work.

Of course, I can truncate all strings used with XtVaSetValues, but this
is untidy, and does not fix the problem.


Simon
--
+----------------------------------------------------------------------+
|  Simon Carter: 3rd Year Elec/Comp Sci, Monash University, Clayton    |
|           Net: simon@auspost.com.au                                  |
|    ___  @mail: 14 Canterbury Rd, Heathmont, Victoria 3135, Australia |
|   (o o) Quote: /simon% find -greatquotes -print >>.signature         |
+ooO-(_)-Ooo-----------------------------------------------------------+


































Xref: sparky comp.windows.x.motif:8323 comp.software-eng:5201
Newsgroups: comp.windows.x.motif,comp.software-eng
Subject: User Interface Design Techniques and Documentation Guidelines
From: vrm@hawksnest.cerc.wvu.wvnet.edu (Vasile R. Montan)
Date: Mon, 4 Jan 1993 21:46:44 GMT
Organization: Concurrent Engineering Research Center

   I am looking for specific references for User Interface Design
using Object Oriented techniques and the Model-View-Controller
paradigm.  However, I would also be interested in any user interface
design strategies or examples of good design documents.

   Most of the user interface design books that I have seen
concentrate on the aesthetics of design, which widgets to use under
various conditions, how to organize the various widgets on the screen,
and other hardware mapping details.  What I am looking for is what
comes before that.  I realize that there are no "cookie cutters" for
design, but there must be some guidelines out there.  We are also
planning to use C++, so I would appreciate the design to be object
oriented.

   What I have in mind are guidelines which would assist a designer in
making the following decisions based on the software requirements:

1. The model needed for the application, and the programmer's
   interface to this model.

2. How that model will be visualized on a computer screen.

3. How the model will be manipulated by the user through the user
   interface.  (ie. the functionality of the system.)

Of course the desisions made in #2 and #3 would break down further and
eventually get to the hardware bindings.

   Once all of these decisions are made, how is it best documented?
Is it best to separate discussions of the model, view and controller?
Or, should discussions be broken down by functionality?  How can
visualations be specified without restricting hardware bindings?  etc.

   I have done design before, but this is my first user interface
design and I feel that it should somehow be different.  I also feel
the previous designs that I have participated in were inadequate
because much of it seemed forced to fit in the document and we were
making many design decisions well into implementation.  However, I do
not know how they could have been improved and have never studied a
good design.

-- Vasile
From: proulxs@socrates.cs.athabascau.ca (Stephane Proulx)
Newsgroups: comp.windows.x.motif
Subject: Re: Undo in XmText
Date: 9 Jan 93 21:41:13 GMT
Organization: Hydro-Quebec, Baie-Comeau, Securite des Barrages

susanh@gvlf4-w.gvl.unisys.com (Susan Hancock) writes:

>Any suggestions on how to implement an Undo feature for a text 
>editor application using the XmText widget?  If not, how about 
>an Undelete feature that is only responsible for the last deletion?

>Thanks in advance.

>Susan Hancock

I'm developping an editor that is using the XmText widget and the way that I am
implementing the UNDO feature is to create an integral copy each time 
we do a modification (Using XmNmodifyVerifyCallback).
Newsgroups: comp.windows.x.motif
From: <cpearce@nemesis.acs.unt.edu> (Chris Pearce)
Subject: Dialog pops up but is very very tiny
Organization: University of North Texas
Date: Fri, 8 Jan 1993 00:27:16 GMT

Motif 1.1.? X11R4 HPUX 8.0

I am writing an application that needs a custom dialog to pop up. I have
written my routine guided by examples in O'Reilly Vol 6. The problem is
that when the dialog pops up, it is the minimum size. Manually resizing the
dialog reveals all the components in their glory.

I read and tested a bit, and I found that if I made the child of the
DialogShell a PushButton, the dialog would be the correct size, but if I
made the child of the DialogShell a Form containing only a PushButton,
the Dialog would pop up the minimum size. What's happening?

Here's my test code.

..
XmString s0;
Widget shell, form, pushb;

shell = XtVaCreatePopupShell ("Dialog...",
    xmDialogShellWidgetClass, toplevel /* Shell returned by XtVaAppInitialize*/,
    XmNdeleteResponse, XmDESTROY,
    NULL);

form = XmCreateForm (shell, "Form", NULL, 0);
XtManageChild (form);

s0 = XmStringCreateSimple ("What is happening, anyway?");
pushb = XmCreatePushButton (form, "Pushb", NULL, 0);
XtVaSetValues (pushb,
    XmNlabelString, s0,
    NULL);
XtManageChild (pushb);
XmStringFree (s0);

---

If I remove the form creation and reparent the pushbutton, things work fine.
I wondered about my parenting the DialogShell with the ApplicationShell,
since Shells are supposed to have only one child, but the source code
presented in Vol 6 for help_text.c parents the DialogShell with
GetTopShell (w), where w is the widget the user activated in order to
get the dialog and GetTopShell () walks up the widget hierarchy until
it finds the first WMShell (which, in the example program would be
toplevel, I think).

--
Chris Pearce, cpearce@nemesis.acs.unt.edu
Xref: sparky comp.windows.x.motif:8461 comp.windows.x:20951 comp.sys.hp:14692
From: mike@inti.lbl.gov (Michael Helm)
Newsgroups: comp.windows.x.motif,comp.windows.x,comp.sys.hp
Subject: rubber band lines
Date: 9 Jan 1993 05:20:27 GMT
Organization: N.I.C.E.
Distribution: inet
Reply-To: mike@inti (Michael Helm)
NNTP-Posting-Host: 128.3.128.82

This is a rather trivial question but I hope someone can steer me
towards some understanding.  I can't seem to get rubber band lines to
happen on an HP-UX X server (some post 8.0 HPUX OS, using mwm, I think
with whatever xllr-level HP ships, PA & non-PA).  The same kinds of
client code work on other X servers like X11R5 on a sun, openlook &c
-- it's not the code, but how the different X servers feel about it,
it seems.  I've tried some really simple low level things, such as out
of Johnson & Reichard, without getting anything to happen in HPUX
land.  I'd appreciate some advice or trivial examples that should work
in an HPUX environment.  What I don't know about X seems to fill
volumes -- please be merciful!

Thanks,
==mwh

Newsgroups: comp.windows.x.motif
From: timkwan@athena.mit.edu (Unknown)
Subject: RowColumn layout
Keywords: RowColumn layout
Organization: Massachusetts Institute of Technology
Date: Thu, 7 Jan 1993 19:17:49 GMT

I want a RowColumn widget with 6 columns and an indefinite number of
rows.  I want it such that as I add children to the RowColumn, they
are added from left to right in the current row, then when the row is
full, go down to the next row.  Example:

	1	2	3	4	5	6
	7	8	9	10	11	12
	13	14	15	16	17	18
	19	20	21	22	23	24
	25	26	...

How do I specify the resources for RowColumn to do that.  I have:

	XmNpacking,     XmPACK_COLUMN,
	XmNnumColumns,  VARIABLES_NUM_COLS,
	XmNorientation, XmHORIZONTAL,

but that doesn't do what I want.  Please send responses to me directly
(other than to the newsgroup).  Thanks.

-Tim
From: tornick@gdc.com (Ed Tornick)
Newsgroups: comp.windows.x.motif
Subject: Motif window management
Keywords: C++ Motif Windows
Date: 8 Jan 93 20:17:18 GMT
Reply-To: tornick@gdc.com
Organization: General DataComm, Middlebury CT

A group of us recently developed a prototype system that used OpenLook and 
DevGuide on the SUN.

Although DevGuide helped us build the actual windows, we needed a way to manage
the windows and their interactions. To this end we developed a C++ class which handled the details of this management. Each window that we build would then inherit this
base class. The base class managed creation of multiple instances of a given window,
stored ptrs to the children windows, handled the destruction of children windows, etc.

We are now building a prototype using C++ and Motif. Rather than re-write the
OpenLook code that managed the windows we are looking for a package (either public
domain) or commercial that we can use to manage the window architecture.

We are using Xdesigner for the actual contruction of the individual windows.

Any information would be appreciated.

Thanks.
 




Newsgroups: comp.windows.x.motif
From: sglanger@vela.acs.oakland.edu (LANGER STEVEN C)
Subject: errors in Vol. 6 Motif Manual
Organization: Oakland University, Rochester MI.
Distribution: na
Date: Mon, 4 Jan 1993 23:07:42 GMT


  Since Heller's Motif Manual is the de facto Bible for a lot
of Motif hackers, I suggest that we update each other on errors in
the book as we find them. I'm sure this will help Mr. Heller out
when the time comes for the 2'nd edition and it may save some of
us some headaches. To start;

pg. 141, Example 5-5
	text = XmStringCreateSimple (dialog, mssg);
-------------------------------------^
This function only takes one arg, namely the "text".


pg. 152 Example 5-10

	while (answer==0)
		XtAppProcessEvents (app, XtIMAll);
---------------------------------^
No "S" on this function

--best regards, steve


	

-- 
Steve Langer  			       sglanger@argo.acs.oakland.edu (VMS)
Oakland University		       sglanger@vela.acs.oakland.edu (Ultrix)
---------------------------------------------------------------------------
Standard disclaimers apply. In addition, the author makes no guarantees,
concerning the grammatical accuracy of his writing. Therefore, any ^B's, ^C's, 
midword character additions/deletions and other non-sense which occurs (after 
the work leaves the author's decade old text editor via his decade old Amiga, 
struggles through a local 1200 baud Merit server to be further mauled via the 
remote VAX mail servers) is someone elses problem - namely yours.
---------------------------------------------------------------------------
From: cq377@cleveland.Freenet.Edu (David C. Williss)
Newsgroups: comp.windows.x.motif
Subject: X/Motif Option Menu Problem
Date: 6 Jan 1993 05:22:59 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Distribution: inet
Reply-To: cq377@cleveland.Freenet.Edu (David C. Williss)
NNTP-Posting-Host: hela.ins.cwru.edu


I have a Macintosh running AUX.  We reciently compiled X11R5
and suddenly got problems with Option Menus (Motif 1.1.x)
The cascade button is shoved all the way to the left, not leaving
any room for the label string, which is then drawn on top of the
option menu.  This only happens on the AUX system.

On other systems I get another problem.  After selecting something
from the option menu, it replaces the contents with the new selection
but instead of centering within the cascade button, it shoves it into
the lower left corner.

Any help would be appreciated (except help with spelling)


-- 
		-Dave Williss
---------------------------------------------------------------------------
Standards are great!  Everybody should have one of their own!
Newsgroups: comp.windows.x.motif
From: rfrench@Xenon.Stanford.EDU (Robert S. French)
Subject: XmText cursor sticking around (1.2.1)
Organization: Computer Science Department, Stanford University.
Date: Thu, 7 Jan 1993 00:13:18 GMT

I'm having a lot of trouble with the Motif 1.2.1 XmText widget.  If I
have multiple XmText widgets in some kind of form, and hit "TAB" when
the cursor is "on" in one of the widgets, the cursor stays there
(unblinking).  When I hit "TAB" when the cursor is "off", it stays
gone.  This allows you to have non-blinking cursors in all of your
text widgets simultaneously, which is ugly at best.  I'm pretty sure
it's not just my application since the demos do it too.  Any hints on
how to fix this?

			Rob

Newsgroups: comp.windows.x.motif
From: emcoop@bnr.ca (hume smith)
Subject: Re: FAQ?
Organization: Bell-Northern Research, Ottawa, Canada
Date: Mon, 11 Jan 1993 21:12:12 GMT

In article <1993Jan11.200713.15764@uc.msc.edu> saroff@uf.msc.edu (Stephen Saroff) writes:

   Where can I get the motif FAQ?

(i know, i know, don't post FAQ answers, but since this can help find the FAQ...)

[Last modified: November 92]

Answer: A number of FAQ's (including this one) are available for anonymous ftp
at pit-manager.mit.edu, 18.172.1.27 under the directory pub/usenet.  (Motif is
under pub/usenet/comp.windows.x.motif) There is also a mail server called
mail-server@pit-manager.mit.edu.  To retrieve a file send mail to the server
with a subject or body similar to

        send usenet/comp.windows.x.motif/Frequently_Asked_Questions_About_Motif_(Part_1_of_3)

This service is looked after by Jonathan Kamens (jik@pit-manager.mit.edu).

It has also been placed in contrib/Motif-FAQ at export.lcs.mit.edu.

The FAQ is also available from csc.canberra.edu.au (137.92.1.1) by anonymous
ftp.  It is in the file /pub/motif/Motif-FAQ

This files are also accessible from WAIS (Wide Area Information System) under
UC-Motif-FAQ, allowing keyword-based searches of the FAQ.
--
Hume Smith                                    My name is little Bongo
hume.smith@acadiau.ca                         I sing my little song-go
emcoop@bnr.ca                                 Rhymes are hard to think of
                                              Except for made-up words like "flong-go"
From: djkeogan@unix2.tcd.ie (Danny Keogan)
Newsgroups: comp.windows.x.motif
Subject: HELP - Sizing of Form Widget
Date: 11 Jan 93 21:08:57 GMT
Organization: Trinity College, Dublin

--------

Should a form widget size itself so as to contain all it's children?

I need to lay out a variety of labels and buttons in a window, I have
been trying to use a form widget but it always pops up tiny. If I
explicitly specify the height and width (XmNheight and XmNwidth) the
layout of the children is OK. 

Any ideas if I can get it to automatically size so as not to clip its
children ??

Please reply by Email to djkeogan@unix2.tcd.ie as I don't get to read
news that often

Thanx in Advance


-- 
Danny Keogan 
Computer Architecture Group
Trinity College, Dublin.

"Those who can do, those who can't simulate!!"
Newsgroups: comp.windows.x.motif
From: daniel@moonshine.osf.org (Daniel Dardailler)
Subject: Re: Dialog pops up but is very very tiny
Organization: Open Software Foundation, Motif Team
Date: Fri, 8 Jan 1993 15:00:18 GMT

 
|> 
|> shell = XtVaCreatePopupShell ("Dialog...",
|>     xmDialogShellWidgetClass, toplevel /* Shell returned by XtVaAppInitialize*/,
|>     XmNdeleteResponse, XmDESTROY,
|>     NULL);
|> 
|> form = XmCreateForm (shell, "Form", NULL, 0);
|> XtManageChild (form);
|> 
|> s0 = XmStringCreateSimple ("What is happening, anyway?");
|> pushb = XmCreatePushButton (form, "Pushb", NULL, 0);
|> XtVaSetValues (pushb,
|>     XmNlabelString, s0,
|>     NULL);
|> XtManageChild (pushb);
|> XmStringFree (s0);
 

Try setting allowShellResize True for the DialogShell, or manage the form
after its kid.

Newsgroups: comp.windows.x.motif
From: drand@spinner.osf.org (Douglas S. Rand)
Subject: Re: getting widgets to re-read resource database
Organization: Open Software Foundation
Date: 11 Jan 93 12:53:47

In article <1993Jan11.143118.10475@afterlife.ncsc.mil> lmpieni@afterlife.ncsc.mil (Lori M. Pieniazek) writes:

   ...
   The problem is that I do not know how to make the widgets re-read their 
   resources from the resouce database that has been just changed, thus, 
   changing their background color. I have tried to unmanage/manage but 
   that does not seem to work.  

   If there is a better way or different way of achieving the same results please
   let me know. I am looking for a way to change all of the widgets after they
   have been created and managed without having to specifically set the value 
   of the background individually for all the widgets.

You cannot without your own code to do it.  Resources are read from
within the Intrinsics code which creates the widget.  Both constraint
and instance resources are obtained at this time.  Of additional
concern are resources which are only valid at creation time (for
instances) or constraint initialize time (for constraint manager).

If the resource database is changed,  and providing that you
can find out about it,  you can walk the database for each 
widget and each resource which you feel is significant so
that you can update it.  Not easy,  but possible,  and this 
would allow you to segregate the changes that should be recognized
from those that should not.

You might take a look at EditRes,  it provides some of this
as part of its functionality.  Another place to see how the
resource database is used is the Wcl code,  which contains
some nice examples of grabbing non-widget resources from the
database.


--
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
From: buzz@bear.com (Buzz Moschetti)
Newsgroups: comp.windows.x.motif
Subject: Yet another "Has anyone created..." Request
Date: 6 Jan 93 14:24:06 GMT
Reply-To: buzz@bear.com (Buzz Moschetti)
Organization: Bear, Stearns & Co. - FAST

Anyone who has worked with popup and option menus knows that they are are
tedious to put together.  The grundiness factor is complemented by a
performance hit when one wants, say, a popup menu to be attached to *many*
widgets.  Conventional programming style would create duplicate menus for
each widget, creating a large number of redundant widgets.

What is needed is an Motif utility to construct popup menus and option
menus on the fly.  Tentative design:

	Widget XmVaCreatePopupMenu(parent, [ resources ,] ...);

If a widget (e.g. a label) wishes to attach the menu, it calls
	XmAttachPopupMenu(label_widget, menu);

Such a design enables us to do this:

	Widget menu_w;
	Widget *mess_of_widgets;
	String choices[] = {"Add","Delete","Copy", 0};
	...
	menu_w = XbsVaCreatePopupMenu(parent_widget,
			XmNtitle,	"Edit",
			XmNalignment,  XmALIGNMENT_CENTER,
			XbsNmenuChoices, choices,
			XbsNselectCallback,  my_callback,
			NULL);

	/* Attach it to all the widgets: */
	for(i = 0; i < max; i++) {
		XbsAttachPopupMenu(mess_of_widgets[i], menu_w);
	}

Anyone care to post something like this?
From: cs4351a@cs.uh.edu (Dr. J C Huang's Class)
Newsgroups: comp.windows.x.motif
Subject: where is the FAQ?
Date: 10 Jan 1993 17:32:41 GMT
Organization: Computer Science dept.,  Univ. of Houston (Main Campus)
Distribution: world
NNTP-Posting-Host: rodin.cs.uh.edu

        Which ftp site carries the most recent version of the FAQ for
	comp.windows.x.motif?

	--
	many thanks,
	Daryl T.
	cs4351a@rodin.cs.uh.edu
Newsgroups: comp.windows.x.motif
From: kshomper@kazoo.cis.ohio-state.edu (keith shomper)
Subject: Re: Menus (and other popups) with debugging
Organization: The Ohio State University Dept. of Computer and Info. Science
Date: Thu, 7 Jan 1993 14:31:37 GMT

In article <1ifi1qINNouh@transfer.stratus.com> lee@deneb.sw.stratus.com (Lee Cooprider) writes:
>
>This feels like a FAQ, but I didn't find it in the list.
>
>Motif causes some popup windows to grab all events when they are active.
>For example, the standard PulldownMenu does this.
>
>When one is debugging the program and it comes to a breakpoint with the
>menu active, a deadlock occurs.  The program is stopped, so the menu items
>cannot be selected, but the program can't be resumed, because the window 
>running the debugger can't get any events.
>
>There must be a standard solution to this problem.  What is it?
>-- 
>Lee W. Cooprider				PP-ASEL/IA
>Lee_Cooprider@vos.stratus.com			Skylane N2908F "Wiley"

When I've run into this problem, I debug the offending program on another
workstation.  dbx or xdbx allows you to do this easily.

Keith