HDTenEightyP/NetNews huggingface dataset:
From: tim@xvt.com (Tim Beres)
Subject: Re: OPEN INTERFACE ?
Keywords: OPEN INTERFACE GUI developer
Organization: XVT Software Inc.
Date: Mon, 31 Aug 1992 18:52:41 GMT
X-Disclaimer: The views expressed in this message are those of an
	individual at XVT Software Inc., and do not necessarily
	reflect those of the company.


In article <5s3eyd2@Unify.Com> grp@Unify.com (Greg Pasquariello) writes:
>In article <wx3ewi4@Unify.Com> you write:
>> 
>> Correct me if I'm wrong, but XVT is based upon the intrinsics (at least in
>> the X world), right?  If that is the case, then it is NOT one of the toolkits
>> that I mentioned above.
>> 
>I'm gonna shoot myself.  I will qualify the above by saying that they
>are the only two that remove dependence upon the intrinsics and ALSO 
>work on MS-Windows, etc.
>
>Sorry Warner!
>
>Greg Pasquariello   	grp@unify.com 	        Sometimes you're the windshield

Ye gods.  I think my last followup I sait "good comments, Greg".
Perhaps I meant Warner.  Pass the gun this way when your done.

But... Other toolkits (XVT included) DO remove you from dependence on
Xt and work under Windows, et al.  XVT may be coded on Xt, but
as an application programmer, you don't need to care 99% of the time.

Tim (I think I'm still me anyway).


-- 
-----------> Tim Beres   tim@xvt.com    Software Consultant
I do not speak for XVT Software Inc.
From: regala@sunfse.ese.lmsc.lockheed.com (Ruby R. Regala)
Newsgroups: comp.windows.x.motif
Subject: Adding items to a List widget, using UIL.
Date: 26 Aug 92 20:37:12 GMT
Distribution: ca
Organization: LOCKHEED, Sunnyvale, CA

I'm using UIL and I'm having a problem using list widgets.

   In my .UIL file I create my main window and it's children
   where each child has a series of pushbuttons(cascade buttons).  
   Associated with each pushbutton is a callback routine which adds
   the selection to the List widget.  My problem is I keep
   getting a segmentation fault on the XmAddItemsUnselected() call.
   Help!!

   sample of the uil:
	XmBulletinBoard {
		arguments {
			blah;
			blah;
			etc;
		};
		controls {
			XmMenuBar	menu;
			XmList   	list_widget;
			etc;
		};
	};
	menu:  XmMenu {
		arguments {
		};
		controls {
			XmCasCadeButton menu1;
		};
	};

	menu1:  XmCascadeButton {
		arguments {
		};
		controls {
			XmCascadeButton selection1;
			XmCascadeButton selection2;
		};
	};

	selection1:  XmCascadeButton {
		arguments {
		};
		callbacks {
   ------------>	XmNactivateCallback = procedure addtolist();
		};

	list_widget:  XmList {
		arguments {
			XmNx = 100; 
			XmNy = 100; 
		};
	};

	Main and  CALLBACK FUNCTION:
	---------------------------
	/* Global Variables */
	Widget   list_widget;

	main()
	{
		etc;
		etc;
	}

	void addtolist(widget,string,position)
	Widget	widget;
	char	string[];
	int	position;
	{
  	   XmString  motif_string;
	   XmString  Str2XmString();   /*converts a 'C' string to a motif string */


		motif_string = Str2XmString(string);
    --------->  XmListAddItemUnselected(list_widget, motif_string, 1);
    |		XmStringFree(motif_string);
    |	}
    |		
    |		
    |		
    ----------- I'm using the list widget as the widget to add the
		item to. I declare it in the .c file as a global.
		It doesn't seem to like the call to XmListAddItemUnselected();
		Hence the segmentation fault(core dumped) error.
		Any clues?

     ***Sorry that this is soooo long!	

     THANKS in advance... any help is enormously appreciated.
     Ruby	
     regala@sunfse.ese.lmsc.lockheed.com
Newsgroups: comp.windows.x.motif
From: achan@idaho.tdd.sj.nec.com (Amy Chan  x2941)
Subject: Re: Help me with chidren widgets
Organization: NEC-AM TDD, San Jose, California
Distribution: inet
Date: Wed, 26 Aug 1992 20:03:49 GMT

In article <9208261511.AA00895@D012S436.sniap.mchp.sni.de> <Ikhtyar.Ansari@sniap.mchp.sni.de> writes:
>
>	My problem is as follows. I have for eg a RowColumn widget with say
>many label and text widgets in it.All the widgets are realized and managed.
>Now starting from the RowColumn widget I want to access the children widgets
>ie the label and text widgets.Is there any way in Motif 1.1 Release 4.0
>by which one could get the Widget ids of the children widgets when one has the
>widget ID of the parent ??
>

For X11R4, you can use the following:

    WidgetList children;
    Cardinal num_children;

    XtVaGetValues(parentWidget, XtNchildren, &children,
                XtNnumChildren, &num_children, NULL);

which will return the children as a widget list and the number of children
on that list.

Hope this helps.
--
Amy Chan                 | E-Mail:
NEC America              |  INET: achan@tdd.sj.nec.com
110 Rio Robles           |  UUCP: ...{decwrl,oliveb}!necsun!achan
San Jose, CA 95134       |
Newsgroups: comp.windows.x.motif
From: chris@ods.com (Chris Atkins)
Subject: Re: Multicolor Application Icons.
Organization: Optical Data Systems, Inc.
X-Newsreader: Tin 1.1 PL5
Distribution: inet
Date: Fri, 28 Aug 1992 13:58:27 GMT

Andrew Purshottam (andy@autodesk.com) wrote:
: Hi, has anyone had any luck defining a multicolor icon using the 
: XmNiconPixmap resource and XPM? I have a nice icon that sxpm displays
: in many colors, but when I install it as my application Icon it comes out in 
: black and grey.
: 
I used the XmNiconWindow resource.  I created a window, allocated the colors 
for the pixmap and converted the XPM structure to a pixmap.  I set the pixmap as
the background pixmap for the window so that the server would take care of 
expose event processing for me.  This worked fine when my porgram was iconic, 
however, if you are using an icon box, I could not get the icon displayed when
the porgram is active to be anything other than the standard icon.

Could tell me where to get info on the XPM routines?

Chris Atkins
chris@ods.com 
Xref: sparky comp.windows.x.motif:6016 comp.unix.aix:9402
From: e-sink@uiuc.edu (Eric W. Sink)
Newsgroups: comp.windows.x.motif,comp.unix.aix
Subject: Really flaky Motif/AIX problem
Date: 4 Sep 92 18:21:48 GMT
Article-I.D.: news.Bu2GCG.GMH
Reply-To: e-sink@uiuc.edu
Organization: University of Illinois at Urbana
Originator: sink@ux2.cso.uiuc.edu

Symptom:	Dialogs have garbled titles, or no title, when displayed
		to remote displays.  Random crashes on the model 560
		only.

Saga:		I had a model 220, with AIX 3.2.2, and I built our app
		using the ICS Motif libraries.  The link used shared
		libraries.  I shipped the executable to a few people,
		and all went fine, except for those who could not run
		it on AIX 3.1 systems because of the shared library
		problems.

		Politics required a change to a 320H, with AIX 3.2 (there
		does not appear to be another version digit anywhere).
		At the same time, I decided to build a static executable.
		I inadvertently built the thing with ICS' Motif library,
		but with the AIX libX11 and libXt.  I shipped this to a
		few people, and some reported crashes when running
		on the model 560.  The previous version did not do this.
		Others reported problems with dialogs having garbled titles.
		On our local system, dialog boxes have very garbled titles,
		or, when displayed to a Sun using OpenWindows 3, no title.
		I assumed that these problems came from incompatibilities
		with ICS' Motif and the AIX libXt/libX11.  All of the above,
		refers to running the app on the RS/6000, simply displaying
		to different places using the DISPLAY env variable.

		So I rebuilt, using ICS' libXt and libX11.  Then I found that
		their libX11.a looks for the XKeysymDB file in a weird place:
		/usr/lpp/motif_R5/usr/lib/X11/XKeysymDB.  So, I get lots of
		warnings messages about missing osfBackspace keysyms and so
		on. After clearing this up, I tried displaying to a remote
		display, and the dialogs are STILL messed up.

		I am unable to duplicate the correct behavior of the original
		compile, using any combination of libraries on the 320H.
		I am unable to verify the test results from the 560, since
		we don't have one.  When running on our 320H here, and
		always displaying to that same 320H, everything is fine.

		(Which is safer in AIX, when shipping executables ?  Shared
		libraries, or static links ?  I assume the latter, but...)

ANY insight or explanations pertaining to the above mess would be much
appreciated.

Thanks in advance,

-- 
Eric W. Sink, Spyglass        | "Kill 'im.  Kill 'em all." - Cpt. James Hook
1800 Woodfield Drive          |
Savoy, IL  61826              |
---- e-sink@uiuc.edu ---------|---------- 217-355-6000 -----------------------
From: larsoe@vccsouth26.its.rpi.edu (Eric Dennis Larson)
Newsgroups: comp.windows.x.motif
Subject: Differences between Motif 1.0 & 1.1
Date: 2 Sep 92 17:21:51 GMT
Article-I.D.: rpi.1axyvb#

I would like to know if there is a list available anywhere with the differences
between Motif 1.0 and 1.1. I have a program that I wrote under 1.0 and it
compiles fine under 1.1, but when I run it, it gives me a Segmentation fault.
Has anyone experienced simillar problems? I'm really not sure what I should
change in the program to make it work.
                                                                 ______
      ___                                                (__)   /      \
     (__   _   ` _        Eric Larson                    (oo)  (  Moo?  )
     (____/ )_/ (__       1003 Caldwell Hall      /-------\/ --'\______/
     ______________       (518)276-4672	         / |     ||
    (______________)      larsoe@rpi.edu	*  ||----||
                                                   ^^    ^^
Newsgroups: comp.windows.x.motif,comp.windows.x
From: imp@solbourne.com (Warner Losh)
Subject: Re: OPEN INTERFACE ?
Keywords: OPEN INTERFACE GUI developer
Organization: Solbourne, User Interface Group
Date: Fri, 28 Aug 1992 00:35:47 GMT

In article <914ep5z@Unify.Com> grp@Unify.com (Greg Pasquariello) writes:
>OI is Open Interface by Solbourne.

Object Interface.  I'm sure you were confused by all the marketing
people that really like to use the word "Open" in product names. :-)

Warner
-- 
Warner Losh		imp@Solbourne.COM
I've almost finished my brute force solution to subtlety.
Newsgroups: comp.windows.x.motif
From: chris@ods.com (Chris Atkins)
Subject: Re: color background image for widgets
Organization: Optical Data Systems, Inc.
X-Newsreader: Tin 1.1 PL5
Date: Mon, 31 Aug 1992 20:54:37 GMT

danny khen (danny@virgo.math.tau.ac.il) wrote:
: Hello Xperts,
: 
:      I would like to set a color image to be the  background
: of  widgets  (diverse  -  shells,  pushButtons,  ...).   The
: closest I get is use the backgroundPixmap resource, but this
: only  works  for  xbm  files  (which are 1-bit deep images),
: displaying them with the foreground & background  colors  of
: the widget. This is not good enough for my application.
: 
:      I'll be grateful for any clue.  Please  e-mail  answers
: to the address in the signature.
: 
You can create a pixmap of the desired depth, place the image into the pixmap
and then set the backgroundPixmap resource to be the value of the pixmap 
containing the image.  Placing the image into the pixmap must be done outside of
motif.  If you are using UIL, you can create multi color pixmaps in UIL and 
have them read in for you.  You might look at the XPM routines for loading
multicolor pixmaps.

Chris Atkins
chris@ods.com
Newsgroups: comp.windows.x.motif
From: scott@statsci.com (Scott Blachowicz)
Subject: Re: .motifbind, XKeysymDB and shipping an application
Reply-To: scott@statsci.com
Organization: Statistical Sciences, Inc., Seattle, WA USA
Date: Sat, 29 Aug 1992 21:12:43 GMT

>>>>> "Greg" == Greg Holmberg <greg@thirdi.UUCP>

 Greg> However, it seems we do need to ship the .motifbind and XKeysymDB files.
 Greg> XKeysymDB goes in /usr/lib/X11 or /usr/openwin/lib.  This will
 Greg> apparently require root permission (which we find undesirable).
We have, too.

 Greg> Is it really necessary to for the customer install this file
 Greg> (XKeysymDB)?
Kind of. With X11R4, the path to that file is hardcoded into the X libraries.
You can, however, substitute your own version. What I've done recently is take
the file mit/lib/X/XStrKeysym.c (and a .h file that it includes) and modify it
for my own purposes. That source is a real simple one that sucks in the
XKeysymDB file using the Xrm routines. I changed it so that it sucks in our
version of the file, then reads in either $XKEYSYMDB or /usr/lib/X11/XKeysymDB
on top of it. (there appears to be code in X11R5 that looks at $XKEYSYMDB).
That way we should get any vendor-specific keysyms that a user has on their
system. We then explicitly load in the .o file for that ahead of searching the
X11 libraries.

--
Scott Blachowicz    Ph: 206/283-8802x240      USPS:  Statistical Sciences, Inc
                                                      1700 Westlake Ave N #500
scott@statsci.com / uunet!statsci!scott                Seattle, WA USA   98109
..or..     Scott.Blachowicz@seaslug.org
From: dave@eagle.smec.Sony.COM (David Jarrin)
Newsgroups: comp.windows.x.motif
Subject: (none)
Date: 28 Aug 92 21:09:14 GMT
Distribution: inet
Organization: The Internet


Greetings!

I would like to respectfully request your help with managing pulldown menus.
My name is David and I am relatively new to Motif Programming. I am pretty
familiar, however, with the general workings of "menus" in Motif. I am
currently working with X11R5 and Motif 1.1.4 on a SUN-SPARC2.

First a little background: I create my pulldown menus in a structure like this,

     MenuBar ---> CascadeButton --> PulldownMenu --> PushButton(s)

Then I setup a "mnemonic" in my CascadeButton to allow me to "pulldown" the
menu either with the mouse or by pressing some "Meta-?" key press combination.

This works great as long as my "Pointer" (i.e. my mouse pointer) remains 
within the application window where the pulldown menu resides. As you probably
already guessed, my problem arises when I move my mouse pointer to a different
application window.

I have tried seting up translations and I am able to "XtManageChild" the menu,
but all the wonderful functionality that the CascadeButton automatically 
handles is gone (i.e. the behavior of my menu is very primitive and I would
have to do quite a bit of coding to try to imitate what the CascadeButton does).

I also tried sending an XEvent to the CascadeButton to make it think that a 
mouse click was executed, but I did not have much luck. Maybe I just did not 
doit right. Sending X events is my weak point.

I tried a couple of other things but I got nowhere.

I would really appreciate it if you could give me some clue as to how to solve
this "puzzle", and from now I thank you for taking the time to read this.

Regards!

David Jarrin
SONY Medical Systems
dave@smec.sony.com
From: vaxtosv@rks.se
Newsgroups: comp.windows.x.motif
Subject: Re: Getting toggle buttons side by side
Date: 27 Aug 92 10:08:08 GMT
Organization: RKS Data AB, Vaxjoe, Sweden

In article <26AUG199216415965@cvdv73>, fisk@cvdv73 (Tom Fisk, 2D-337 STM, 5-4341) writes:
> I am trying to define a series of toggle buttons side by side so they look 
> like a grid of boxes.  I am using the UIL and ... as you guessed ... am not
> having any luck.  My question is what XmN resources need to be set and to
> what value?  I have tried the marginWidth, marginHeight, borderWidth without
> any good results.  The best I have been able to do is get them about 1 pixel
> apart.  
> 
> Is there a different widget I should be using?  I would use the DrawnButton
> but that does not provide the on/off functionality that I want.
> 
> Thanks for your help!   Tom.
> ------------------------------------------------------------------------------

I would suggest you place your ToggleButtons in a RowColumn widget.
Set the following resources on your widgets:

XmRowColumn:
  XmNpacking:	    XmPACK_COLUMN | Make all TB's same size                
  XmNnumColumns:    2             | Number of rows                         
  XmNspacing:	    0             | Distance between ToggleButtons         
  XmNmarginHeight:  0  | Distance between TB and RC's top and bottom       
  XmNmarginWidth:   0  | Distance between TB and RC's left and right sides 
  XmNorientation:   XmHORIZONTAL  | Spreads out horizontal in two rows     

XmToggleButtons:
  XmNborderWidth:    1            | Gives you gridline-look

Six ToggleButtons created with these resources set will look like this:

+-----+-----+-----+
| Tb1 | Tb2 | Tb3 |
+-----+-----+-----+
| Tb4 | Tb5 | Tb6 |
+-----+-----+-----+
				Yet another Tom
-- 

      +-------------------------+   +-------------------------+
      |  Tom Svaleklev           \ /  E-mail: vaxtosv@rks.se  |
      |  RKS Data AB, Box 209     X   Phone : +46 470 47062   |
      |  S-351 05 Vaxjo, Sweden  / \  Fax   : +46 470 48976   |
      +-------------------------+   +-------------------------+
Newsgroups: comp.windows.x.motif
From: shmdgljd@rchland.vnet.ibm.com (Jay Schmidgall)
Subject: XmList partial hilite of item?
Date: Mon, 31 Aug 1992 20:53:54 GMT
Reply-To: jay@vnet.ibm.com
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM Rochester, MN

Is it possible* to select part of an item in an XmList?  That is, I have a
list with say 20 items in it.  I would like to select or have highlighted
just the 5th through 12th characters of the second item, for example.

* and if it is, how.

-- 
: jay          jay@vnet.ibm.com    My opinions and ideas, not my employer's.
: shmdgljd@rchland.vnet.ibm.com    (c) Copyright 1992.  All rights reserved.
Newsgroups: comp.windows.x.motif
From: stgprao@st.unocal.COM (Richard Ottolini)
Subject: key events in Motif 1.1 on Sun don't seem to work
Organization: Unocal Corporation
Date: Wed, 26 Aug 1992 23:37:33 GMT


Translations like <Btn1Down> will jump to the action,
but anything I try with <Key> in it doesn't do anything.
Is this a known bug, or might I be missing a some code?
Newsgroups: comp.windows.x.motif
From: jxt@stc06.ctd.ornl.gov (TOLLIVER J S)
Subject: A bug in Motif 1.1 option menus?
Reply-To: jxt@stc06.ctd.ornl.gov (TOLLIVER J S)
Organization: Oak Ridge National Laboratory
Date: Wed, 2 Sep 1992 16:28:03 GMT

I have noticed a strangeness with Motif 1.1 option menu callbacks. I
challenge you to get Dan Heller's simple_option.c source in O'Reilly
Vol 6, ch 16 (available from export.lcs.mit.edu) to experience this
yourself.

In that code, he builds an option menu using the XmVaCreateSimpleOptionMenu
function. This option menu behaves nominally. Click and drag to another
menu item works nominally. A quick click on the little box at the right of
the menu posts the menu, which can the be selected from with a click in the
chosen menu item. A quick click on the button itself (i.e., to the left of the
little box but still in the button) doesn't post the menu but does call the
callback for that menu item.

Now, modify the example to build the option menu using the method suggested
in the OSF Programmer's Guide -- i.e., first make a pulldown menu with
buttons for each of the desired menu items and then call XmCreateOptionMenu,
setting the XmNsubMenuId to be the pulldown menu. Like so:

    pdmenu = XmCreatePulldownMenu (rc, "pdmenu", NULL, 0);

    button = XtVaCreateManagedWidget ("button_0",
xmPushButtonWidgetClass, pdmenu, XmNlabelString, line, XmNmnemonic, 'D',
NULL);
    XtAddCallback (button, XmNactivateCallback, option_cb, (XtPointer)
0);

    button = XtVaCreateManagedWidget ("button_1",
xmPushButtonWidgetClass, pdmenu, XmNlabelString, square, XmNmnemonic,
'S', NULL);
    XtAddCallback (button, XmNactivateCallback, option_cb, (XtPointer)
1);

    button = XtVaCreateManagedWidget ("button_2",
xmPushButtonWidgetClass, pdmenu, XmNlabelString, circle, XmNmnemonic,
'C', NULL);
    XtAddCallback (button, XmNactivateCallback, option_cb, (XtPointer)
2);

    ac = 0;
    XtSetArg (args[ac], XmNlabelString, draw_shape); ac++;
    XtSetArg (args[ac], XmNsubMenuId, pdmenu); ac++;
    option_menu = XmCreateOptionMenu (rc, "om", args, ac);

With this modified code, a quick click in the little box behaves as described
above. But, a quick click in the button itself both posts the menu AND CALLS
THE XmNactivate CALLBACK FOR THAT MENU ITEM! That is, the activate callback
gets called BEFORE the user has even selected one of the menu items! Then
selecting the current menu item calls the activate callback again!

Is this a bug or am I totally missing something here? If a bug, is it a known
bug? The only work around I have found is to also set arm and disarm callbacks
on each of the buttons in the pulldown menu and keep a count of the calls to
the arm callback. If the count is 2 when the activate callback is entered, do
nothing -- it is the fake activate when the menu is being posted. If the count
is 0 or 1, then go ahead and run through the callback code. Be sure to reset
the arm count back to zero in the disarm callback. This works but is UGLY!

Are there any other work arounds?

Thanks,
Johnny Tolliver
Oak Ridge National Laboratory
jxt@ornl.gov
Newsgroups: comp.windows.x.motif
From: hudson@hp750.itg.ti.com (Steve Hudson)
Subject: Re: Keyboard support for popup menues
Date: Mon, 31 Aug 1992 16:16:53 GMT
Organization: IEF Development, Texas Instruments Inc., Plano Texas
X-Disclaimer: This message was written by a user at Texas Instruments Inc.
              The opinions expressed within are those of the user and not
              necessarily those of Texas Instruments.
From: lohia@prathvi.EBay.Sun.COM (Raj Lohia)
Newsgroups: comp.windows.x.motif
Subject: Changing keyboard focus in motif, Help!!
Date: 26 Aug 1992 00:22:19 GMT
Organization: Sun Microsystems, Inc.  Mt. View, Ca.
Distribution: world
Reply-To: lohia@prathvi.EBay.Sun.COM (Raj Lohia)
NNTP-Posting-Host: prathvi.ebay.sun.com



Is there any way in motif, can I change keyboard focus to my 
program's window without having user using pointer to change focus
and regardless of window manager focus policy.

I tried using XSetInputFocus in my program but it didn't work.

I will appreciate any help/info.
 
Thanks

-Raj
lohia@prathvi.sun.com
Newsgroups: comp.windows.x.motif