Path: utzoo!attcan!uunet!husc6!rutgers!okstate!romed!drd!mark
From: mark@drd.UUCP (Mark Lawrence)
Newsgroups: comp.windows.x
Subject: menuTest5 fix
Keywords: bad XtNumber call
Message-ID: <285@drd.UUCP>
Date: 6 Oct 88 22:19:03 GMT
Reply-To: mark@drd.UUCP ()
Distribution: na
Organization: in *this* company!?
Lines: 29

Sorry if somebody's already posted this.  I didn't see it go by.  The
menuTest5 program that comes with the new hp widgets blows up on my Sun
3/50.  A call to XtNumber on the args parameter was returning 30 when in
fact only 1 arg was being passed.  Context diff follows:
*** menuTest5.c.orig	Thu Oct  6 17:11:50 1988
--- menuTest5.c	Thu Oct  6 17:12:09 1988
***************
*** 169,175 ****
                                     panes[0], NULL, 0);
     XtSetArg (args[0], XtNkbdAccelerator, "Ctrl<Key>b");
     btns[3] = XtCreateManagedWidget("btn3", XwmenubuttonWidgetClass, 
!                                    panes[1], args, XtNumber(args));
     btns[4] = XtCreateManagedWidget("btn4", XwmenubuttonWidgetClass, 
                                     panes[2], NULL, 0);
     btns[5] = XtCreateManagedWidget("btn5", XwmenubuttonWidgetClass, 
--- 169,175 ----
                                     panes[0], NULL, 0);
     XtSetArg (args[0], XtNkbdAccelerator, "Ctrl<Key>b");
     btns[3] = XtCreateManagedWidget("btn3", XwmenubuttonWidgetClass, 
!                                    panes[1], args, 1);
     btns[4] = XtCreateManagedWidget("btn4", XwmenubuttonWidgetClass, 
                                     panes[2], NULL, 0);
     btns[5] = XtCreateManagedWidget("btn5", XwmenubuttonWidgetClass, 


-- 
	Mark Lawrence
		[uunet!apctrc,romed,tulsun]!drd!mark
			mlawrence@jarsun1.ZONE1.COM         (918)743-3013