HDTenEightyP/NetNews huggingface dataset:
From: fkmunker@cip.informatik.uni-erlangen.de (Frank Munkert)
Newsgroups: comp.windows.x.motif
Subject: Re: Application shell position
Date: Tue, 5 Jan 1993 08:10:24 GMT
Organization: CSD., University of Erlangen
Distribution: inet
NNTP-Posting-Host: faui00a.informatik.uni-erlangen.de
Keywords: Motif

>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. 

Thanks for your many replies! The solution to the problem is
quite simple:

      Application.geometry: +50+50

---
Frank Munkert            |  Uni Erlangen
Zum Froschbruecklein 5   |  
8500 Nuernberg 10        |  <fkmunker@cip.informatik.uni-erlangen.de>
Germany                  |  or: <ln_fmu@pki-nbg.philips.de>
Newsgroups: comp.windows.x.motif
From: sglanger@vela.acs.oakland.edu (LANGER STEVEN C)
Subject: Re: Capturing the Close Gadget
Organization: Oakland University, Rochester MI.
Distribution: na
Date: Mon, 4 Jan 1993 22:56:09 GMT


  I've done a little more work with Heller's example. First of
all, replace the dialog arg in XmAddWMProtocalCallback with
something of a char nature (ie. "text"). That gets you
past the compiler. 

Then , when the window is created, if you did what I did and
used XtVaCreateManagedWidget, you'll get the notice that

Warning: Must be a vendor shell.

Hmmm. So I used exactly Heller's code;
	dialog = XmCreateWarningDialog (parent, "notice", args, 2);

and Tada, it worked. But my original purpose  was to create a simple
drawing area. I tried;

	dialog = XmCreateDialogShell
and 
	dialog = XmCreateDrawingArea

and these both yielded our friend
	Warning: must be a vendor shell.

Further testing revelas that the only thing (apparently) tha
IS a recognized vendor shell is

	dialog = XmCreateWarningDialog
and	dialog = XmCreateInformationDialog.


So my question know is, how can I use (essentially) Hellers example
for a shell dialog?

-- thanks in advance, 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.
---------------------------------------------------------------------------
Newsgroups: comp.windows.x.motif
From: quinton@stna.dgac.fr (Marc Quinton STNA 7SU p8046 BD24)
Subject: Re: Undo in XmText
Organization: Service Technique de la Navigation Aerienne
Date: Mon, 11 Jan 1993 08:59:34 GMT

In article <1993Jan8.163416.9520@gvl.unisys.com>, 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


You could have a look at a simple Motif based editor named "Jetedit". The is a
undo feature is this program. 

-- 
 _____________________________________________________________________________
|   ___    ___   |                  |                                         |
|  /__ \  / __\  |   QUINTON Marc   | Technical Department of Civil Aviation  |
|   __\ \/ /     |__________________|_________________________________________|
|  / __   |   _  |                  |                                         |
|  \ \_\   \_//  |   Evry France    | e_mail : quinton@stna7.stna.dgac.fr     |
|   \___/\___/   |                  |                                         |
 -----------------------------------------------------------------------------
Newsgroups: comp.windows.x.motif
From: liuxia@wam.umd.edu (New VaxHacker)
Subject: MrmNcreateCallback documentation?
Organization: University of Maryland, College Park
Date: Sat, 9 Jan 1993 17:18:24 GMT

	I am trying to find the functionality of MrmNcreateCallback.
I looked at the UIL programming guide but couldn't find any explanation
for it. Any help would be greatly appreciated. 
	
	liuxia@wam.umd.edu 
Newsgroups: comp.windows.x.motif
From: drand@spinner.osf.org (Douglas S. Rand)
Subject: Re: Warning from XtRemoveGrab
Organization: Open Software Foundation
Distribution: inet
Date: 7 Jan 93 10:56:02

In article <"21613.93.01.06.13:06*.S=Hellan.PRMD=notis.ADMD=TELEMAX.C=NO."@MHS> Hellan@notis.telemax.no (Jon K?re Hellan) writes:

   I have a problem when popping down Motif dialogs.

   From some dialogs, I call time consuming callbacks. Early in the callback,
   I pop down the dialog with the following sequence:

	   XtPopdown(shell_widget);
	   XmUpdateDisplay(shell_widget);

   At the end of the callback, the dialog is destroyed.

   Sporadically, I get the warning:

	   Warning: XtRemoveGrab asked to remove a widget not on the list

   I am not quite sure, but I think there have been core dumps shortly after this.

   I introduced the popdown to give better feedback to the user. Previously, the
   dialog did not disappear until the dialog was destroyed at the end of the
   callback.

Well,  the message from XtRemoveGrab might be appearing in a 
case that has been fixed in some recent releases of Motif.  This
shouldn't (by itself) cause a crash.  Best of recollection is that
this is fixed in 1.1.5 and 1.2.1,  but I don't know definitively.

Using XtPopdown and XtPopup is problematic for some of Motif shells.
You haven't specified the class of the Shell you are using.  Some
of Motif's shells require you to manage the child to post the shell.
Others,  in fact,  demand the use of XtPopup.  So it depends.  It
is documented.
--
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
Newsgroups: comp.windows.x.motif
From: ch_purzl@rcvie.co.at (Klaus Puerzelmayer)
Subject: Problem: Scrolling a button with a Pixmap
Reply-To: ch_purzl@rcvie.co.at
Organization: Alcatel ELIN Research
Date: Mon, 11 Jan 1993 17:03:34 GMT

Hi!
I am trying to  assign a pixmap to a PushButton. The Pixmap was created with the bitmap editor.
I use the XReadBitmapFile call to import the Pixmap and the SetArg,SetValue mechanism and XtCreateWidget to create the PushButton with the Pixmap. Everything works fine on 
a monochrome display, scrolling this button which is assigned to a form is no problem.
But when I do this on a color screen the following happens as soon as the button 
appears on the screen:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  62 (X_CopyArea)
  Serial number of failed request:  6698
  Current serial number in output stream:  6806

Has anyone of you encountered the same problem ?

Thanks Klaus.


----------------------------------------------------------------
Klaus Puerzelmayer		e-mail: ch_purzl@rcvie.co.at
Tool Development		voice:  +431/391621-272
Alcatel-Informatics		fax:    +431/391452
Ruthnergasse 1-7, A-1210, Wien
Austria
----------------------------------------------------------------
Newsgroups: comp.windows.x.motif
Newsgroups: comp.windows.x.motif
Subject: Keyboard Traversal
From: mcintyre@nrlvx1.nrl.navy.mil
Date: 7 Jan 93 15:42:01 -0400
Organization: NRL SPACE SYSTEMS DIVISION

   I am checking the keyboard traversal of my apllication right now and things
seem to work as expected, except...

   How do you determine the order in which the widgets are traversed within a
shell?  I thought it was by position, i.e. moving from the upper-left hand
corner to the lower-right hand corner of the shell; but that does not appear to
be the case all the time and it certainly is not the desired behavior all of
the time.  How do you change this??

   Second problem is very specific.  I have the following widget strucutre:

   XmDialogShell--
                 |
                 ->XmPanedWindow--
                                 |
                                 ->XmScrolledList
                                 |
                                 ->XmForm--
                                          |
                                          ->XmPushButton...

This is just a simple dialog with a scrolled list widget and 3 pushbuttons, OK,
Apply and Cancel.  I have set the OK button to be the defaultButton of the Form
to start with and this works.  What does not work is using the RETURN key
within the scrolled list.  The item looks selected, but when I programmatically
query the widget for the selected item, I get back a NULL value.  Using the
SPACE key to select an item in the scrolled list works perfectly fine, but not
the RETURN key.  I assume that there is a conflict in the Translations between
the default pushbutton and the use of the defaualt key inside the scrolled
list.  However, I have not dealt with translations to any degree, (I have been
avoiding them), and do not want to delve into them unneccesarily.  BTW the
scrolled list widget is a single select list.  Does anyone know a simple
answer, or any answer, for this problem??

                        Sean T. McIntyre

Newsgroups: comp.windows.x.motif
From: lanzo@tekelec.com (Mark Lanzo)
Subject: Changing background color of objects & associated labelPixmaps
Organization: Tekelec Inc., Raleigh NC
Date: Tue, 12 Jan 1993 16:58:57 GMT

A quick question for you:  is there a way to change the XmNbackground
color for a label widget or derived class and have it automatically
remake the labelPixmap for the widget using the new background color?

I have an application where I create "icons" in a drawing area;
these "icons" are actually XmDrawnButton widgets.  Each button
has a XmNlabelType = XmPIXMAP, and the actual XmNlabelPixmap is 
specified (by name) in the application resource file.

This works fine when the widget is first created - the widget
constructor builds an appropriate labelPixmap for the widget
by fetching a bitmap and constructing a pixmap for the widget
using the widget's foreground and background colors. 

This works fine until I want to change the color of an "icon"
at run time - I can do an SetValues call on the widget with a 
new XmNbackground value, but this does not cause a new pixmap
to be generated for the widget.  The background color changes;
but the old pixmap remains, so all I usually see is a colored
border around the pixmap where the margin area of the widget
is visible.

My solution to this problem has been to simply destroy the old
widget and create a new one in its place with the new desired
background color, and other resources taken from the original 
widget.  This strikes me as inelegant - is there a better solution?

I am curious also as to what you think the appropriate behavior
for a widget should be in this case.  If a widget created its own
labelPixmap from a *bitmap* in the image cache, should changing
the background color regenerate the pixmap?  [Obviously regenerating
the pixmap in other cases, such as when you explicitly provide
a XmNlabelPixmap in code, would NOT make sense.]  Should there
be a separate function available to do this?

For reference, this is under X11R4 with Motif 1.1 (1.1.4 I think).

Thanks in advance.

   --	Mark Lanzo  KD4QLZ  lanzo@tekelec.com

Replies please to "lanzo@tekelec.com".  Our newsfeed is flaky at best;
I may never see a posted response.
From: snail@lsl.co.uk
Newsgroups: comp.windows.x.motif
Subject: Re: MrmNcreateCallback documentation?
Date: 11 Jan 93 17:51:41 GMT
Organization: Laser-Scan Ltd., Cambridge

In article <1993Jan9.171824.3426@wam.umd.edu>, liuxia@wam.umd.edu (New VaxHacker) writes:
> 
> 	I am trying to find the functionality of MrmNcreateCallback.
> I looked at the UIL programming guide but couldn't find any explanation
> for it. Any help would be greatly appreciated. 
> 	
> 	liuxia@wam.umd.edu 

It gets called when the widget is created as a result of a call to
MrmFetchWidget(TAG) or MrmFetchWidgetOverride(TAG). The callback passes the
widget id, the client data TAG, and a callback structure to the callback.
Your callback should then remember the widget id for use later. 

Hint, set the tag value up to be a pointer to an object, in the callback cast
the tag to be the pointer and then store your widget id in this object. Bingo!
no global variables. Easy.

byeeee
-- 
snail@lsl.co.uk      

"Washing one's hands of the conflict between the powerful and the powerless
 means to side with the powerful, not to be Neutral."
                                                     Quote by Freire.
                                                     Poster by OXFAM.
From: sllkz@cc.usu.edu
Newsgroups: comp.windows.x.motif
Subject: Please help with PopupShell problem!!
Date: 10 Jan 93 16:51:50 MDT
Organization: Utah State University

Hi all,
	I have compiled a Motif program on hp 9000/700 running hp unix. Iam 
popping a window using XtVaCreatePopupShell, it has a form as a child. The form
holds a text widget and an PushButton. 
	The problem: The application runs fine except when the Popup window is
invoked I get the message
Error: Unresolved inheritance operation

and the application terminates. I have looked at the code but have not found
the bug yet. Actually I have compiled and run this same program on a different
architecture successfully. 
	Please help. Thanks in advance!!
Krishna
From: stroyan@hpfcso.FC.HP.COM (Mike Stroyan)
Date: Thu, 7 Jan 1993 23:37:40 GMT
Subject: Re: specifying a visual class and depth
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.windows.x.motif

Andrew Congdon writes-
> The FAQ for comp.windows.x.intrinsics has a section on using a
> non-default visual.  I used this to implement a "-visual" option.  I
> still had problems with an HP720 CRX-24 which refused to believe that it
> had a TrueColor class visual despite xdpyinfo telling me it had one (is
> this why HP don't supply xdpyinfo?).  I added a "-depth" option and used
> XGetVisualInfo(3) to search for the visual with desired depth.

The CRX-24 has PseudoColor and DirectColor visuals.  It doesn't have
a TrueColor visual.  TrueColor is a non-dynamic subset of DirectColor
functionality.

Mike Stroyan, mike_stroyan@fc.hp.com

P.S. xdpyinfo is shipped in /usr/contrib/bin/X11 as of release 9.0.
Newsgroups: comp.windows.x.motif,comp.software-eng
From: soltys@cs.unc.edu (Mitchel Soltys)
Subject: Re: User Interface Design Techniques and Documentation Guidelines
Organization: UNC Office of Information Technology
Distribution: usa
Date: Wed, 6 Jan 1993 21:36:52 GMT

|>    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.
|> 

I would also like to see some information on this topic. It's one thing to write
a large and complicated program under something like X. It's quite another to
also make the code reusable etc. and to abstract it well enough that you minimize
rewrite if you change your toolkit or graphics engine. 

Newsgroups: comp.windows.x.motif
From: jo@eco.twg.com (Jo Heiden)
Subject: Child widgets not resizing on an XtVaSetValues call to topshell
Summary: Child widgets do not resize when topshell is grown with XtSetValues
Keywords: resize, shell
Organization: The Wollongong Group (East Coast Operations)
Date: Mon, 4 Jan 93 21:55:05 GMT

	I have an application which consists of a topshell widget with a form
widget on it.  The form has several child widgets on it that are attached to the
appropriate sides of the form, so that when the topshell widget is resized the
children are resized correctly.  The problem is occassionally. (99% of the time
it works fine), when I resize the topshell widget through an XtVaSetValues,
the shell is resized but the form and its children are not.  Has anyone else
seen this and is there a fix?

	Any hints would be greatly appreciated...

				Thanks, Jo
Newsgroups: comp.windows.x.motif
From: sglanger@vela.acs.oakland.edu (LANGER STEVEN C)
Subject: motif text widgets
Organization: Oakland University, Rochester MI.
Distribution: na
Date: Wed, 13 Jan 1993 04:08:03 GMT

Hi folks;
  Another question, this time on text widgets. I have a dialog with
several one line text widgets attached to it. To the right of each
text widget is a button. When the button is pressed, I want new text to show
up in the assocaited text widget.

________________________________________________
|
| text1 b1
| 
| text2 b2
|
|

the code fragment is
{
	dialog = XmCreateDialogShell (toplevel, ...

	form = XmCreateForm (dialog, ...

	text1 = XmCreateTextWidget (form, attach upper left
	b1  = XmCreatePushButton (form, attach to right of text widget

	XtAddCallback (b1, XmNactivateCallback, cbfunc, "b1");
	XtManageChild (form);
	XtManageChild (dialog);
}

void cbfunc (Widget w, XtPointer data, XtPointer dummy)
{
	char *text;
	char str[]="here i am";

	if (strcasecmp(data, "b1") == 0)
	{
		temp = XtMalloc (sizeof(str));
		temp[sizeof(str)] = 0	;	/* null terminator */
		XmTextSetString (w, text);
		XtFree (text);
	}

}

This is my adaptation of Heller's example 15-2 file browser.c
program. The cbfunc is based on read_file.


The dialog is created and the default text is drawn, but when the b1
is pressed, I get a core dump and dbx zeros in on the
XmTextSetString call.

Any ideas on how to beat this?

--thanks in advance, 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.
---------------------------------------------------------------------------
Newsgroups: comp.windows.x.motif
From: drew@sscvx1.ssc.gov
Subject: Any way to make DrawingWidget hardcopy?
Organization: Superconducting Super Collider Laboratory
Date: Mon, 11 Jan 1993 20:45:41 GMT

I'm sure that this must have come up before, but I cannot find any
reference in FAQ....I want to make a hardcopy of the stuff in a 
drawing widget - turning it into a postscript file for printing would
be just great.  Is there anything available for this?
Newsgroups: comp.windows.x.motif
From: t8122aa@cd1.lrz-muenchen.de ()
Subject: XmVaCreateSimpleOptionMenu
Keywords: option menu
Organization: Lehrstuhl fuer Hochspannungstechnik, TU Munich
Date: Fri, 8 Jan 1993 14:04:10 GMT
Reply-To: carsten@hsa.e-technik.tu-muenchen.de

Hi folks,
we're trying to create an option menu (like the one in the periodic example) with
XmVaCreateSimpleOptionMenu but without using the uil stuff.  Parent is a RowColumnWidget.
 Could you please give  us a complete example (including XmOptionButtonGadget).
 Thanks  so far.  
   carsten  


Newsgroups: comp.windows.x.motif
From: clements@athena.cs.uga.edu (Brian Clements)
Subject: Scrolling Text
Organization: University of Georgia, Athens
Date: Sun, 10 Jan 1993 22:12:11 GMT


Hi,

This should be an easy question for many of you all.  I am new to Motif
and I am trying to implement a scrolling text window.  I do not need cursor
movement or anything fancy.  (very similar to a VT100)  I just need to
be able to print to it and to have it echo key strokes.  In what direction
should I look?  A multi-line Text widget?  

Any guidance would be appreciated.

Thanx,
Brian 
:-)
--------------------------------------------------------------
brian@cosmic.cosmic.uga.edu
From: snail@lsl.co.uk
Newsgroups: comp.windows.x.motif
Subject: Re: Problems with XmDeleteAllItems
Date: 5 Jan 93 11:43:01 GMT
Organization: Laser-Scan Ltd., Cambridge

In article <1i9q9jINNbpn@fbi-news.Informatik.Uni-Dortmund.DE>, joergens@snorre.informatik.uni-dortmund.de (Ulrich Joergens (PG211)) writes:
> Hello,
> 
> 1)
> I have some problems with XmDeleteAllItems under motif1.1.
> Calling this function evokes a core dump.
> Even an old workaround (for X11R3) doesn't work anymore.
> 
> Are there any bugs known and if so are there any workarounds?

Workaround is:-

	XmListDeselectAllItems(widget_id);
	XmListSetPos(widget_id); 
	XmListDeleteAllItems(widget_id);

The first of the three lines may not be needed, I can't remember.

> 
> 2)
> How can i explicitly give the input focus to a widget when it pops up?

Use XmProcessTraversal(widget_id, XmTRAVERSE_CURRENT);
See the man page.
-- 
snail@lsl.co.uk      

"Washing one's hands of the conflict between the powerful and the powerless
 means to side with the powerful, not to be Neutral."
                                                     Quote by Freire.
                                                     Poster by OXFAM.
From: rik@misty.boeing.com (Rik slaven)
Date: Mon, 4 Jan 1993 22:06:25 GMT
Subject: Changing the Text Widget's Cursor
Organization: Boeing Commercial Airplane BCS Support
Newsgroups: comp.windows.x.motif



Is there a 'simple' way to change the cursor inside of a
text widget?  My users want something more visible than
the 'i-beam'.  I didn't notice an appropriate resource
in the Motif Programmer's Reference.

Thanks.
Newsgroups: comp.windows.x.motif
From: updike@bug.cat.com (Michael Updike)
Subject: Re: Problem with activating windows
Reply-To: kahlers@ncsa.uiuc.edu
Organization: Caterpillar, Inc - CIM Services, Peoria, IL  USA
Date: Fri, 8 Jan 1993 00:11:27 GMT

In article <1993Jan7.172542.23112@fzi.de>, xiong@fzi.de (Xiong Xun) writes:
|> Am I landed in the right group for my following question:(?)
|> 
|> what I'd like is that each window under my mwm should always be activated 
|> automatically where the cursor is going to! Until now I've always to
|> make an additional mouse click to achive this. There was no such problem
|> under the my TWM before I changed my to MWM.
|> 
|> Any hint for this novice question is very appreciated! Thankx in adv!
|> 

Mwm*keyboardFocusPolicy:	pointer
Newsgroups: comp.windows.x.motif