HDTenEightyP/NetNews huggingface dataset:
From: navid@synoptics.com (Navid Razavi)
Subject: Internationalization in Motif ?!
Reply-To: navid@synoptics.com
Organization: Synoptics Inc. Santa Clara, California.
Date: Wed, 18 Nov 1992 02:50:57 GMT




Is there any document to port Motif code to other languages? e.g  Kanji, German ,...

In X11R5  has mutliplebyte (mb) and wide-character(wc) versions of many 
functions that are used to manipulate or display strings: 
XDrawString to XmbDrawString, XwcDrawString.

I know that Sun uses gettext,strcoll, strxfrm..... and OSF uses catopen, catget,...

But I haven't seen any specific document on USER INTERFACE  PART!!
I need general MOTIF guide lines:
	Use implicit layout. Use library Calls.
	Don't hard code position, font, height of objects and more ....
	Widget to support multiplebyte,...

Thanks in advance .
:-)
----------------------------------------------------
Navid Razavi   Sr. Software Engineer                   	Tel: 408-764-1663 (O)
	       SynOptics Communications Inc. 
	       4401 Great America Pkwy
	       Santa Clara, CA 95052            E-mail: navid@synoptics.com 
				navid@leland.stanford.edu  
     "I love my job but I 'd rather be windsurfing."
      News Group : rec.windsurfing



Newsgroups: comp.windows.x.motif
From: murphy@ufp.dco.dec.com (Rick Murphy)
Subject: Re: POSITIONING of dialog boxes. How do I do that ???
Reply-To: murphy@ufp.dco.dec.com
Organization: Digital Equipment Corporation, Landover MD
Distribution: comp
Date: Sun, 15 Nov 1992 18:50:29 GMT


Grab the mxrn source - decuac.dec.com:/pub/DEC/dxrn.tar.Z - and unpack it.
Routine "xthCenterWidgetOverCursor" does what you're asking for.
I've cut the relevant sections and included 'em below.
(The IMPORTANT bit is that you set XmNdefaultPosition to false on the
dialog. You're setting it to true, so it gets centered over the
parent.)
	-Rick

void
xthCenterWidget(widget, x, y)
Widget widget;
int x, y;
{
#ifdef MOTIF
    Arg sargs[3];
#else
    Arg sargs[2];
#endif
    Arg gargs[2];

    XtSetArg(gargs[0], XtNwidth, 0);
    XtSetArg(gargs[1], XtNheight, 0);
    XtGetValues(widget, gargs, XtNumber(gargs));

    x -= ((int) gargs[0].value) / 2;
    y -= ((int) gargs[1].value) / 2;
    if (x + (int) gargs[0].value > WidthOfScreen(XtScreen(widget))) {
	x = WidthOfScreen(XtScreen(widget)) - (int) gargs[0].value;
    }
    if (y + (int) gargs[1].value > HeightOfScreen(XtScreen(widget))) {
	y = HeightOfScreen(XtScreen(widget)) - (int) gargs[1].value;
    }
    if (x < 0) {
	x = 0;
    }
    if (y < 0) {
	y = 0;
    }
    XtSetArg(sargs[0], XtNx, x);
    XtSetArg(sargs[1], XtNy, y);
#ifdef MOTIF
    XtSetArg(sargs[2], XmNdefaultPosition, False);
#endif
    XtSetValues(widget, sargs, XtNumber(sargs));
    return;
}

void
xthCenterWidgetOverCursor(widget)
Widget widget;
/*
 * center a window over the cursor
 *
 *   returns: void
 *
 */
{
    Window root, child;
    int x, y, dummy;
    unsigned int mask;

    (void) XQueryPointer(XtDisplay(TopLevel), XtWindow(TopLevel),
			 &root, &child,
			 &x, &y, &dummy, &dummy,
			 &mask);

    xthCenterWidget(widget, x, y);
    return;
}

--
Rick Murphy, WA1SPT/4			Washington Open Systems Resource Center
Domain:  murphy@dco.dec.com -or- murphy@burfle.enet.dec.com
Bang:    decwrl!burfle.enet!murphy	"Somewhere between 30 and Death" -
Ding:	 (301) 918-5883				bumper sticker.
Disclaimer: This nonsense came from an AI program written in TECO. Ignore it.
Newsgroups: comp.windows.x.motif
From: koverber@bigmax.ulowell.edu (Kurt Overberg)
Subject: Hyper-widget
Organization: University of Massachusetts at Lowell
Distribution: comp
Date: Tue, 17 Nov 1992 20:42:14 GMT



Hello, 

	There was something posted here about a year ago called
hyper-widget.  It was a hypertext-like text widget.  Is there a 
comp.sources.motif or something where I could find this?  If 
anyone has ANY information about this, please email me.  Thanks!


					-kurt
--
Kurt Overberg            | Opinions expressed here are MINE!           
U of Mass, Lowell        | "Poke a double-decker on a Llama taboot,       
koverber@cs.ulowell.edu  |  Llama taboot, taboot!"      -Phish
Newsgroups: comp.windows.x.motif
Subject: Query about the Command widget
From: sands@ccu1.aukuni.ac.nz (Greg Sands)
Date: Tue, 17 Nov 1992 04:20:03 GMT
Reply-To: g.sands@aukuni.ac.nz
Organization: University of Auckland
Keywords: command

I have a small problem with the XmCommand widget that I cannot see how to fix.
The difficulties occur when a previous item in the list has been selected and
executed.  I can now deselect that item OK, but what I want is that when I next
press the up-arrow key, the selected item will be the last one in the list. 
Instead, it the one immediately before the one previously selected, as if the
item had not been deselected at all.  It seems as though the 
SelectionBoxUpOrDown action routine may be the one to look at, but how would
I modify it to do what I want?  Basically it would be sufficient to over-ride
the first arrow-key press, and force it to select the bottom item.

Thanks for any help you can give with this.

Greg.


-- 
Greg Sands.                           |  Department of Engineering Science
-----------                           |  University of Auckland           
g.sands@aukuni.ac.nz                  |  New Zealand.
Newsgroups: comp.windows.x.motif
From: drand@spinner.osf.org (Douglas S. Rand)
Subject: Re: OptionMenu Problem
Organization: Open Software Foundation
	<9848@blue.cis.pitt.edu.UUCP>
Date: 18 Nov 92 17:26:43

In article <9848@blue.cis.pitt.edu.UUCP> nr3m+@pitt.edu (Matthew A Henry) writes:

   System: HP705, HP-UX 8.07, Motif 1.1

   I have a window that contains groups of labels, text field widgets,
   toggle buttons, and one option menu.  After using the option menu, the
   text field widgets will no longer become focused or accept any input.
   The toggle buttons continue to work correctly.  If the window is closed
   and opened again, the text field widgets are fine.  Any thoughts on why
   the option menu might be effecting the text field widgets this way would
   be greatly appreciated.

As to what is apparently happening,  I'd say that there is some
problem with focus being lost, and the traversal code is probably
confused.  But Motif 1.1 (not 1.1.3,4,5?) is pretty old at this
point.  Also not stated is whether you are manipulating the
menu and fields with the mouse, keyboard or both.  But I'd say
that you need a more recent Motif version.

--
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: mjo@slee01.srl.ford.com (Mike O'Connor)
Newsgroups: comp.windows.x.motif
Subject: Re: Motif package for Sun
Date: 16 Nov 1992 20:18:53 GMT
Organization: Not an official spokesperson for Ford Motor Co.
Distribution: inet
Reply-To: "Mike O'Connor" <mjo@fmsrl7.srl.ford.com>
NNTP-Posting-Host: slee01.srl.ford.com

In article <HOPS.92Nov16101827@herts.x.co.uk> hops@x.co.uk (Mike
Hopkirk) writes:

:>From: romeo@osf.org
:>If are looking for Motif binaries to run on the Sun you can contact on of
:>the following vendors and they can assist you with that:
:>
:>ICS	617/621-0060
:>Quest	408/496-1900
:>SI Sys	403/264-4343
:ml> Any reason why IXI was left off the list?  
:ml> They offer run-time and development Motif licenses in addition to 
:ml> their X.Desktop product. Just a customer and all that.
:
:We would be quite interested in the answer to that question also.

For that matter, what about DEC's Motif for Sun?

					...Mike


--
 Michael J. O'Connor           |  Internet:  mjo@FMSRL7.SRL.FORD.COM
 Ford Motor Company, OPEO      |  UUCP:      ...!{backbone}!fmsrl7!mjo
 20000 Rotunda, Bldg. 1-3001   |  Phone:     +1 (313) 248-1260
 Dearborn, MI  48121           |  Fax:       +1 (313) 323-6277
Newsgroups: comp.windows.x.motif
From: daniel@moonshine.osf.org (Daniel Dardailler)
Subject: Re:    Motif example source code is wanted!
Organization: Open Software Foundation, Motif Team
Date: Mon, 16 Nov 1992 16:55:39 GMT

In export.lcs.mit.edu:/pub/R5untarred/contrib/Motif,
you'll find some good examples of Motif code.

daniel@osf.org
Newsgroups: comp.windows.x.motif
From: CJSENFT@lexmark.com
Subject: Selecting multiple list items by position
X-Disclaimer: These views are the poster's and not necessarily those of Lexmark
Organization: Lexmark International, Lexington, KY
Date: Fri, 20 Nov 1992 19:37:39 GMT

 
We are interested in our programs being able to select items in an
XmEXTENDED_SELECT List Widget by Position. The Items in the list are
not unique so we cannot use XtVaSetValues(wid, XmNselectedItems, ....).
I have also attempted calling XmListSelectPos inside a loop but each call
deselects the previously selected item and XmListSetAddMode does not seem
to have any effect (other than letting the user move the selection focus
with the keyboard arrows). Any Suggestions would be appreciated.
 
Thanks,
Cathy J. Senft     cjsenft@lexmark.com
From: wright@mscf.med.upenn.edu
Newsgroups: comp.windows.x.motif
Subject: Transparent Backgrounds
Date: 19 Nov 92 16:11:52 GMT
Organization: Univ of Penn - Med School Computer Facility

Greetings,

I am having trouble trying to set a drawing area background to
transparent.  I have tried setting it to None, but that does
not seem to work.

My basic need to to display a drawing area widget on top another
one, and I need the lower widget to show through.  I am
implementing a graphic timeline and objects on the timeline.  The
entire area of the object widget erases the timeline underneath it.

Any suggestions would be greatly appreciated.  I have checked the
FAQ and found nothing.  Perhaps this would make a good FAQ topic?

Thanks.

Charles Wright
no sig.
Newsgroups: comp.windows.x.motif
From: reza@loki.jsc.nasa.gov (Reza Razavipour)
Subject:  xmFileSelectionBox
Organization: Lockheed
Date: Mon, 16 Nov 1992 22:32:01 GMT

Has anybody seen the following warning message:

Warning: _XmPopWidgetExtData: no extension found with XFindContext.

It comes up when I create a xmFileSelectionBox who is a child 
of a xmDrawingarea. I create and manage and destroy and I create again and
I get the above message.
If you have any clues e-mail me you reply.
Thanx a bunch.
Reza.
Newsgroups: comp.windows.x.motif
From: "ed carroll" <ed.carroll@canrem.com>
Subject: gui jobs
Reply-To: "ed carroll" <ed.carroll@canrem.com>
Organization: Canada Remote Systems
Distribution: comp
Date: 20 Nov 92 12:19:25 EST

We are currently experiencing a demand for xwindows motif developers
that is simply overwhelming.

If you have paid professional experience in this field, here is an
excellent resource to help you in your job search.  The jobs listed
require at least 1 yr work experience though.


Free JOB LISTINGS ONLINE for MIS, Data Processing, and SW Engineering.
                              Career Systems Online
             Call  with your modem              413 592 9208  N-8-1  HST
                Positions available all over the United States
24 hours a day   No cost or obligation at all   Member NAPC
fax 413 592 9255

---
  OLX 2.2  Career Systems Online   413-592-4069   HST
--
Canada Remote Systems  - Toronto, Ontario
World's Largest PCBOARD System - 416-629-7000/629-7044
From: cindy@SSD.CSD.HARRIS.COM (Cindy Walters)
Newsgroups: comp.windows.x.motif
Subject: Problem with WM_DELETE_WINDOW callback
Date: 19 Nov 92 19:27:53 GMT
Distribution: comp
Organization: Harris Computers Systems Division, Fort Lauderdale,FL
NNTP-Posting-Host: hcx1.ssd.csd.harris.com


I am working on a Motif user interface to a large, multi-window
application.  I'm experiencing a problem when I try to handle the window
manager (mwm) "Close" system menu item - I do not want the window to be 
immediately destroyed, rather I want to handle this situation in my own
callback.  

I have been able to implement the behavior I want in a very simple, small
Motif sample program which is very similar to the real application in the
way it creates the various toplevel windows.  However, when I transfer this
code to my large application, it does not work :-(  More specifically, I am 
able to get the window to "do nothing" when I select the mwm "Close" system 
menu, but the callback that I have set up for this protocol does not appear 
to be getting called when the "Close" system menu item is selected.  Maybe 
someone can give me some suggestions on what to try?  (I'm using X11R4 and 
Motif 1.1.4.) 

Please email, and I will summarize if there is interest.  Thanks !


Here's an example of the code I'm using:
  Atom         wmDeleteWindow ;
  Widget       shell, new_window ;
  [...]
  shell      = XtCreatePopupShell("mywindow", 
                                  topLevelShellWidgetClass, AppShell, 
                                  args, argcnt) ;
  new_window = CreatemyWindow(shell) ;    /* create and manage widgets */
               XtManageChild(new_window) ;
               XtPopup(shell, XtGrabNone) ;

                 /* I want to handle the wm Close item. */
               XtVaSetValues(shell, XmNdeleteResponse, XmDO_NOTHING, NULL);

                 /* Set up my callback for this protocol. */
               wmDeleteWindow = XmInternAtom(XtDisplay(shell),
                                            "WM_DELETE_WINDOW",
                                            False) ;
               XmAddWMProtocolCallback(shell,
                                       wmDeleteWindow,
                                       (XtCallbackProc)myCloseCB,  
                                       (caddr_t)new_window) ;

I have a 'printf()' statement in myCloseCB() to see if it ever gets that
far, but it never does.  

Any ideas?  Thanks for considering this :-)

Cindy Walters
cindy@ssd.csd.harris.com
Newsgroups: comp.windows.x.motif
From: zmed0b@trc.amoco.com (Michael E. Dupree)
Subject: Re: Scrollbars
Originator: zmed0b@zircon
Keywords: XmScrollbars, Scrolledwindows, colors
Organization: Amoco Production Company, Tulsa Research
Date: Mon, 16 Nov 1992 16:01:11 GMT


In article <1992Nov13.153606.8923@cc.gatech.edu>, rdk@cc.gatech.edu (Bobby Krupczak) writes:
> Hi!
> 
> Im using a scorlledwindow to display "stuff" and want to set the
> scrollbar color to black.  I have tried all possible programmatic and
> app-defaults options I can think of but still get gray scrollbars.
> 
> Does anyone have pointers to how I can set the scrollbars to black?
> 
> Thanks,
> 
> Bobby
> 
> 
> 
> rdk@cc.gatech.edu

I have not had this problem myself, but I might take a guess that using
XtGetValues to get the widget ID of the appropriate scroll bar (for example,
XmNverticalScrollBar) could be the first step.  Depending on what you wanted
to do, I know that you can set the trough color and some other stuff using
XtSetValues.  Just a guess.
Newsgroups: comp.windows.x.motif,comp.windows.x
From: wallsj@CS.ColoState.EDU (jeffrey joel walls)
Subject: X Events
Originator: wallsj@CS.ColoState.EDU
Date: Tue, 17 Nov 1992 22:10:52 GMT
Organization: Colorado State University, Computer Science Department
Keywords:  Focus Change Events


I'm sorry if this is a FAQ, but I am trying to write a Motif/X
program that will allow a user to click on another window so that
I can grab information about that window.  The trouble is, I lose
the focus for *my* window.  I know there is a way to do this
(xwd does it), but I cannot for the life of me find it in any 
documentation nor can I figure it out with intuitive thinking.


Thanks in advance,

Jeff Walls

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|       Colorado State University       | 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Jeff Walls - wallsj@CS.ColoState.Edu  |
| 2520 Baxter Place                     |
| Fort Collins, CO  80526               |
| (303) 226-2411                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Newsgroups: comp.windows.x.motif
From: rcal@spsd630a.erim.org (Rita Callaghan)
Subject: library incompatibility question (Motif v1.1.3 to v1.2)
Organization: Environmental Research Institute of Michigan, Ann Arbor, Michigan
Date: 16 Nov 92 10:55:50




	Hello,

	I have a standalone application that I'm having
	problems with.  Not only have we upgraded from SunOS
	v4.1.1 to SunOS v4.1.3, we have also upgraded from
	Motif v1.1.3 to Motif v1.2.  A description of the problem
	is listed below.  I need to know if I am not thoroughly
	defining my widget.  Please send some advice my way!

	thanks,

	Rita C. 

	<--------------------- cut here ------------------>

	My standalone application is heavily Motif-based and
	includes two nonstandard widgets among its widget set.

	One widget is an image widget, and its class rec is
	listed below:

	typedef struct  _XsImageClassRec{
	   CoreClassPart    core_class;
	   XsImageClassPart  image_class;
	} XsImageClassRec;

	This widget is working just fine, no problems have
	been encountered.

	The other widget is a graph widget, whose class rec
	is listed below:

	typedef struct _GraphClassRec{
	        CoreClassPart core_class;
	        CompositeClassPart composite_class;
	        LabelClassPart label_class;
	        GraphClassPart graph_class;
	}GraphClassRec, *GraphWidgetClass;

	The problem I am having seems to be in the CompositeClassPart.
	I am getting a segmentation violation when XmIsGadget (in
	Manager.c) is called.  It seems that core_class.extension is
	pointing to a variable that is not defined.




--
Rita Callaghan
Research Scientist
Environmental Research Institute of Michigan
INTERNET:   rcal@erim.org     
VOICE MAIL: (313) 994-1200 x2282
                         __
   ____          __     /\ \          _____  
  /  \_\        / /\   / / /        / ___ \ \          ____        
 / /\ |_|      / / /  / /_/        / /__/ / /         /\...\       
 \ \/ /_/_    / / /  /  \ \       / ___  / /         / .\...\___   
  \  __ \_\  / / /  / /\ \ \     / /  / / /          \. /. /\...\  
   \ \ \/_/ / / /   \/_/\ \ \   / / // / /            \/._/ .\...\ 
    \ \_\  /_/ /         \ \_\ /_/ //_/ /                 \. /. ./ 
     \/_/  \_\/           \/_/ \_\/ \_\/                   \/._./  
 

Newsgroups: comp.windows.x.motif
From: parikh@enws237.eas.asu.edu (Ripple Parikh)
Subject: Need help with closing windows.
Organization: Arizona State University, Tempe
Date: Thu, 19 Nov 1992 00:00:09 GMT


I am having a hard time resolving a problem. 
My problem is  that whenever the user activates/double-clicks the 'Close' 
option in the window manager menu; I want to do some stuff (like seting/reseting
a flag) before closing the window. In other words, I want to call a function 
which will do some stuff and close the window instead of mwm directly closing 
the window by invoking its 'f.kill' procedure.

Any help/pointers would be greatly appreciated.
Please reply by e-mail.

Thanks.
Ripple.
From: montnaro@spyder.crd.ge.com (Skip Montanaro)
Newsgroups: comp.windows.x.motif
Subject: Re: A suggestion for window popup improvement for mwm
Date: 19 Nov 92 18:44:46 GMT
Reply-To: montanaro@ausable.crd.ge.com (Skip Montanaro)
Distribution: comp
Organization: GE Corporate Research & Development, Schenectady, NY


snail@lsl.co.uk writes:

   For instance, take the simple case of a "WORKING" dailog to appear, the
   user shouldn't need to interact with this dialog at all, except to
   (maybe) hit the "Abort" (or whatever) button. Yet with your proposed
   scheme (which may not yet be fully fleshed out) the user would need to
   interact (in order to access the icon window (I think icon windows are
   BAD NEWS anyway) and bring the working dialog into use.

I agree that requiring extra interaction for dialog shells would be a big
problem, however dialog shells are recognized as different beasts by the
window manager. In my environment I have interactivePlacement set to true,
yet dialog shells still pop themselves up in the middle of my application
without interaction. I imagine mwm can tell the difference between top level
or application shells and dialog shells. I don't envision dialog shells
being subject to my scheme.

In any case, dialogs typically come up quickly, so aren't the problem here.
What is extremely annoying is to have a window take so long to appear (or to
appear completely asynchronously) that I am off doing something else, and
then have a window either pop up between me and the window(s) I'm using at
the moment, or have the window manager grab the pointer and attach a
rectangle to it, requiring my immediate attention - no ifs ands or buts.

I should have also stated in my proposal that this sort of behavior should
be controllable by the user, presumably by changing a resource setting for
the window manager. I guess I took it for granted. I do understand that not
everyone will like the idea.
--
Skip (montanaro@crd.ge.com)
Newsgroups: comp.windows.x.motif
From: richm@netcom.com (Richard Mauri)
Subject: Re: Using Motif Gadgets for drawing primitives
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Fri, 20 Nov 1992 15:05:11 GMT

In article <219@trident.datasys.swri.edu> mark@trident.datasys.swri.edu (Mark D. Collier) writes:
>I need to integrate a simple drawing capability into an application
>(lines, circles, rects, polygons, etc). In the past, I have always
>rendered the primitives with Xlib and used my own lists to maintain
>stacking order and other attributes. Another individual suggested
>(and developed a prototype) using a custom Motif gadget, in which each
>primitive is maintained by a separate instance of the gadget. I
>think this approach will work, but am a little leary of resource
>problems and potential stacking order problems. For example, if a
>set of lines or rectangles overlap one another, can stacking order
>be set as required? I have done this with widgets (which have windows),
>but not gadgets.
>
>Any input appreciated.
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Mark D. Collier                      Southwest Research Institute
>Senior Research Analyst              Automation and Data Systems Division
>Voice: (512) 522-3437                Data Systems Department
>FAX:   (512) 522-5499                Software Engineering Section
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Remember that when you write gadgets, you also must write their
parent container classes also. Since there are many ways to divide
the responsibilities up between the gadgets and their parent, you
have total control over any and all display issues including stacking
order. If you have never written your own widgets and gadgets you 
may feel intimidated and feel it's beyond your reach or you may
think you always need source for the widget set you are subclassing.
I have written may widgets and gadgets using Xt/Xm based objects
and have never had to look at any motif source code. 
The power you gain in this realm is substantial and the consistancy
in design is wonderful for anyone maintraining the code.
I would suggest a good book like the X Window Toolkit by
Asente and Swick for guidlines however.
Rich Mauri
-- 
Richard Mauri               // Not ready to face the winter.
SW Eng / X hack             // Pray for wind.
Trimble Navigation Ltd.     // Pay the bills.
richm@netcom.com	    // Hope nothing breaks
Newsgroups: comp.windows.x.motif