ArrowB.c Current rev 1.17 Last Release 1.12
ArrowB.c 1.17
   date: 1998/02/22 01:00:22;  author: rwscott;  state: Exp;  lines: +6 -2
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
ArrowB.c 1.16
   date: 1997/12/26 21:35:58;  author: u27113;  state: Exp;  lines: +45 -4
   MMF is a script that I use to rebuild makefiles.
   	You need to replace the $HOME/Hungry/LESSTIF part by
   	wherever you hold your sources.
   
   ArrowB* : add trait
   
   Notebook.c : first working version, nothing fancy yet.
   
   notebook/test1.c shows what it does; an example with three pages.
ArrowB.c 1.15
   date: 1997/12/24 03:36:33;  author: rwscott;  state: Exp;  lines: +6 -3
   Protect the Arm action when it is called without an event.
ArrowB.c 1.14
   date: 1997/12/06 12:40:38;  author: rwscott;  state: Exp;  lines: +3 -3
   set_values - type PrimForeground instead of Prim_Foreground.
   	(How did that slip through!!)
ArrowB.c 1.13
   date: 1997/12/05 17:49:21;  author: rwscott;  state: Exp;  lines: +11 -2
   set_values - If the forground or the background changes re-create the
   	GC's


ArrowBG.c Current rev 1.12 Last Release 1.9
ArrowBG.c 1.12
   date: 1998/02/22 01:00:23;  author: rwscott;  state: Exp;  lines: +15 -6
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
ArrowBG.c 1.11
   date: 1998/01/28 20:12:26;  author: u27113;  state: Exp;  lines: +4 -4
   test/Xm/*/Makefile.am : be able to build with 2.0 library as well.
   
   working.html : add reference to BRL/CAD 4.4 which is reported to work.
   
   lib/Xm/(Gadgets) : one pixel sensitivity fixes by Gilles Seguin.
   	+ a new test in test/Xm/arrowbg for it.
   
   CURRENT_NOTES : refer to Xinvest as a demo for 2.0 PanedWindow.
   
   Paned* : the year hasn't been 1995 for a long time. Copyright changed.
ArrowBG.c 1.10
   date: 1997/12/26 21:35:59;  author: u27113;  state: Exp;  lines: +40 -2
   MMF is a script that I use to rebuild makefiles.
   	You need to replace the $HOME/Hungry/LESSTIF part by
   	wherever you hold your sources.
   
   ArrowB* : add trait
   
   Notebook.c : first working version, nothing fancy yet.
   
   notebook/test1.c shows what it does; an example with three pages.


BaseClass.c Current rev 1.9 Last Release 1.8
BaseClass.c 1.9
   date: 1998/02/02 14:57:10;  author: u27113;  state: Exp;  lines: +9 -3
   xmdipmon has a strange way of exiting. I.e. it is the only app I know
   that uses the X11R6 way of doing this.
   
   Side effect #1 : we printed a message from BaseClass.c about not being
   able to pop ExtNode. Removed that in case of widget being_destroyed.
   
   Side effect #2 : we got a NULL pointer that we tried to dereference in
   Vendor.c's destroy(). Fixed that too.


BulletinBoard.c Current rev 1.21 Last Release 1.19
BulletinBoard.c 1.21
   date: 1998/02/22 01:00:24;  author: rwscott;  state: Exp;  lines: +42 -7
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
BulletinBoard.c 1.20
   date: 1997/12/05 23:07:59;  author: u27113;  state: Exp;  lines: +5 -3
   Add a few files to be able to configure the tests too.
   Automake, autoconf should be run nightly on test/* .
   I'll handle that next week.
   
   Futher: a bug fix for Steven Danz's problem with bulletinboard.
   Also added IPE to the list of working apps, fixed a URL too.


CascadeB.c Current rev 1.80 Last Release 1.57
CascadeB.c 1.80
   date: 1998/03/07 21:24:00;  author: rwscott;  state: Exp;  lines: +8 -4
   Some clean up as per the note from Alexander Mai
   
   
   How come I do not see those 'implicit declaration of function' warnings
   anymore?
CascadeB.c 1.79
   date: 1998/03/06 01:17:44;  author: rwscott;  state: Exp;  lines: +6 -2
   _XmCBMemuBarDoSelect - at the end of this we were setting RC_SetArmed to
       false.  This was causing the Grab to be re-installed.  Changed to
       CB_SetArmed False.
CascadeB.c 1.78
   date: 1998/03/05 16:29:04;  author: rwscott;  state: Exp;  lines: +7 -4
   Just say NO to gadgets.
   
   In check disarm we were checking to see if the event y value was greater
   than the widget height.  This works for widgets but not for gadgets, since
   the event is relative to the parent of the gadget.  To tell if we left
   the bottom of a gadget the event must be greater than the XtY + XtHeight.
   
   This fixes the into the menu too fast problem in Mosaic.
CascadeB.c 1.77
   date: 1998/03/01 23:03:15;  author: rwscott;  state: Exp;  lines: +24 -537
   CascadeB[G].c - general cleanup
   
   MenuUtil.c:_XmRC_GadgetTraverseLeft() - It seems that the event that causes
   	this can trigger this more than once.  Protect it with
   	_XmIsEventUnique/_XmRecordEvent.  This is where the strange behaviour
   	of mgdiff's menus during keyboard traversal was coming from.
CascadeB.c 1.76
   date: 1998/02/28 18:41:55;  author: rwscott;  state: Exp;  lines: +70 -2
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
CascadeB.c 1.75
   date: 1998/02/27 22:23:22;  author: rwscott;  state: Exp;  lines: +23 -10
   Get rid of the FixOptionMenu calls.  This is replaced by the RC_MenuProc
   XmMENU_SUBMENU which does essentially the same thing except that it is
   now under the control of RC.
CascadeB.c 1.74
   date: 1998/02/27 13:28:56;  author: rwscott;  state: Exp;  lines: +6 -2
   CascadeBG.c:ArmAndActivate() - currently I use an XmARM_EVENT to show the
   	button as armed. This however sets DragMode to True, so now reset
   	drag mode after the arm.  This will not be a problem when the
   	LabelMenuProcs get written for CascadeBG.
   
   MenuUtil.c:_XmMenuNextItem() - when searching for a valid control just use
   	XmIsTraversable(), it takes care of all of the other cases.
   
   MenuUtil.c:_XmMenuPrevItem() - see above
   
   MenuUtil.c:_XmMenuDisarmItem() - an XmLEAVE_EVENT to a gadget will only draw
   	the gadget un-armed if drag mode is on, therefore force the drag mode
   	to the value needed.  Again, this will not be necessary when the
   	LabelMenuProcs have been written for the Gadget buttons.
   
   RowColumn.c: Disarm the active child during a MENU_SHELL_POPDOWN
CascadeB.c 1.73
   date: 1998/02/27 05:04:21;  author: rwscott;  state: Exp;  lines: +126 -50
   Move most of CascadeButton's knowledge of menus to the RC_MenuProcs. Still
   to go is the knowledge of how to popup a menu.  All that should be done
   from CascadeButton is call the RC_MenuProc XmMENU_CASCADING and RC will take
   care of placing it correctly.  Again I think the code that handles this is
   correct, just misplaced.
CascadeB.c 1.72
   date: 1998/02/25 05:31:02;  author: rwscott;  state: Exp;  lines: +8 -6
   Clean toggleButton out of its intimate knowledge of the menu system.
   Each of the button types seem to have their own little tests when it comes
   to menus, all of which are getting concentrated in RowColumn for a more
   consistent treatment of the menus.
CascadeB.c 1.71
   date: 1998/02/22 21:42:19;  author: rwscott;  state: Exp;  lines: +14 -4
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
CascadeB.c 1.70
   date: 1998/02/22 14:41:54;  author: rwscott;  state: Exp;  lines: +12 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
CascadeB.c 1.69
   date: 1998/02/22 04:42:14;  author: rwscott;  state: Exp;  lines: +14 -2
   Mainly comments as to what is going to be changing wrt the menu system.
   Basicly the way the label menu procs are used right now is wrong.  A label
   does not know if a particular button press is the correct button, this is a
   job for RowColumn, the official menu widget. The same is true for un-posting
   menus.  The label menu procs should be used by Label subclasses that can be
   in a menu system.  Through these procs the RowColumn can arm/disarm the
   controls without having to know the details of the control.
   
   So, what does all this mean.  The current contents of the Label[G] menu procs
   will be moved to RowColumn menu procs.  Label[G] menu procs will be written
   for each of the controls that can be in a menu. After that, nothing should
   care, or even know, about private/public menu shells.  All of this should
   be the responsibility of the routines in MenuShell.
   
   If anyone disagrees, now is the time to speak!
CascadeB.c 1.68
   date: 1998/02/21 01:50:08;  author: rwscott;  state: Exp;  lines: +13 -2
   With this keyboard traversal of menus should be possible. Feedback welcomed!
   
   CascadeB[G].c:ArmAndActivate() - If we post a submenu from a cascade button
   	in a menubar arm the first item in the menu. (Needs to be smarter
   	and arm the first active menu control)
   
   RowColumn.c - change the default radio behaviour back to False. This is wrong
   	according to misc/test16 but until we deal with it in other places
   	it messes up a bunch of toggle buttons in menus. See mgdiff->options
   	for an example.
   
   MenuUtil.c - Write all of the menu traversal handlers.....
   
   ToggleBG.c:[Enter|Leave]Window() - Do not insist on being in DragMode since
   	during keyboard traversal we are not.
CascadeB.c 1.67
   date: 1998/02/20 05:45:19;  author: rwscott;  state: Exp;  lines: +37 -16
   Label.c - get rid of the FocusIn action this is actually in RowColumn
   	  Label still has a few more that need to move to RowColumn
   
   Manager.c:_XmAcceleratorHandler() - When an action proc is called directly
   	you must pass a pointer to the num_params, not NULL
   
   RowColumn - define the FocusIn action proc that was in Label
   
   AnythingElse - Debug stuff
CascadeB.c 1.66
   date: 1998/02/17 13:31:47;  author: rwscott;  state: Exp;  lines: +5 -2
   First cut at keyboard traversal of menus.
   
   CascadeB[G].c:_XmCBMenuBarDoSelect - If we post a submenu then also arm the
   	first item.
   CascadeB[G].c:_XmCBMenuBarSelect - set MGR_ActiveChild for the parent
   
   MenuUtil.c - write a MenuTraversalHandler (A bit of a mess right now)
   
   PushB[G].c - set MGR_ActiveChild when Armed
   
   RowColumn.c - Install the traversal translations on MENU_BAR's.
CascadeB.c 1.65
   date: 1998/02/06 21:15:47;  author: rwscott;  state: Exp;  lines: +11 -10
   _XmCascadingPopup - In the case of option menus, make sure we post them on the
   	screen.  We were allowing them to be posted above or to the left of
   	the screen.  We had a test for this but it was on the wrong end of
   	an if.
CascadeB.c 1.64
   date: 1997/12/21 23:14:47;  author: rwscott;  state: Exp;  lines: +4 -2
   some protection for CascadeButtons without a submenu
CascadeB.c 1.63
   date: 1997/12/21 20:06:00;  author: rwscott;  state: Exp;  lines: +28 -3
   _XmCascadingPopup - Do not use XtTranslateCoords if the button is part of
   	a torn off menu.  The re-parenting seems to confuse Xt.
CascadeB.c 1.62
   date: 1997/12/21 14:16:51;  author: rwscott;  state: Exp;  lines: +23 -5
   This is all with respect to tearoffs.
   
   
   CascadeB.c
   
   	MenuBarEnter - Popdown the old menu only if a menushell (not torn off)
   
   	CascadePopupHandler - make sure the menu is back in its menu shell if
   		it was torn off
   
   	DelayedArm - Do not put a torn off menu back to its menushell here.
   		If the delay never times out then the menu is left in the
   		menu shell and never poped up.
   
   	CheckDisarm - If we have to popdown the menus use popdownEveryone.
   
   MenuShell.c
   
   	change_managed - If there are no managed children we pop down but, we
   	must popdown private shells different from public ones. Same goes for
   	popping up.
   
   	MenuShellPopdownOne - do not restore tear off to its toplevel shell
   	here, it just confuses popdowneveryone.
   
   	MenuShellPopdownEveryone - restore tear offs to their toplevel shells
   	here, after all the menus have been sorted out.
   
   	MenuShellPopupSharedMenuPane - Since we do not use XtPopup for menus
   	anymore we must take care of setting and un-setting of Shell_PoppedUp.
   	Not setting this was messing up <BtnDown> in push button and
   	probably other places (anywhere there was an if (Shell_PoppedUp)).
   
   PushB.c
   
   	Add some debug statements.
   
   RowColumn.c
   
   	DoBtnEventCleanupReplay - Do not call PopdownDone for a torn off menu
   
   	_XmGetActiveTopLevelMenu - Return something usefull for an active
   	tear off.
   
   TearOff.c
   
   	_XmTearOffBtnDownEventHandler - Arm the menu. Something a little
   	strange happens here, see the comments in the source.
   
   	_XmTearOffBtnUpEventHandler - DisArm the menu.
   
   	_XmTearOffInitiate - Get rid of the keyboard and pointer grabs from
   	the previous menu and turn off drag mode.
   
   	_XmAddTearOffEventHandlers - big time guess here! Add a button up
   	handler to the tear off and all of its widget children so we can
   	disarm the menu. Add a button down handler to all of the widget
   	children so we can arm the menu.
   
   	_XmRestoreTearOffToToplevelShell - Do not ungrab things here. The
   	grabs are now taken care of in the event handlers.
   	Do not reposition the shell if an event is not given.  This is due
   	the the MenuShell:change_managed call to put the menu back to the
   	toplevel shell.
   	Make sure the event handlers are in place.
   
   	_XmRestoreTearOffToMenuShell - Time for a little magic here! Ever
   	wonder how Motif keeps a copy of the tear off in the toplevel shell
   	and displays it in the menu at the same time?  Well you just take a
   	copy of the pixels in the toplevel shell before you re-parent the
   	menu and put those pixels into the shell.  Since the menu will have
   	grabs there is no way to interact with it so fake it!
   	I should be able to just set the background pixmap of the shell and
   	have X take care of the copy, stay tuned.
   	Do not unmanage the menu if it is in a private shell, they are always
   	managed.
CascadeB.c 1.61
   date: 1997/12/19 01:30:58;  author: rwscott;  state: Exp;  lines: +15 -2
   CascadeB.c:_XmCascadingPopup - before posting a menu make sure that it is in
   	it menushell.
   
   CascadeB.c:CheckDisarm - If we need to popdown a menu, use MenuShellPopdownOne
   	so that the menu will get restored to its toplevel shell if torn.
   
   MenuShell.c:MenuShellPopdownDone - If the menu is a popup do not unmanage it
   	if it is an active tearoff.
   
   MenuShell.c:MenuShellPopdownOne - If the menu is an active tearoff unpost any
   	menus posted from it and put it back into its toplevel shell.
   
   TearOff.c:_XmDismissTearOff - set the TearOffActive bit to 0
   TearOff.c:_XmTearOffInitiate - set the TearOffActive bit to 1
CascadeB.c 1.60
   date: 1997/12/16 03:18:02;  author: rwscott;  state: Exp;  lines: +24 -4
   CascadeB.c:StartDrag - If we are thinking of posting a menu make sure the
   	menu is put back into its menu shell if it was torn off.
   
   CascadeB.c:DelayedArm - ditto
   
   CascadeB.c:CheckDisarm - If we are thinking of un-posting a menu because
   	we are leaving the cascade button that posted it do not do it if
   	the menu is torn off.
   
   MenuShell.c:MenuShellPopdownEveryone - Do not recurse if the the shell is not
   	a menu shell, ie torn off.
   
   RowColumn.c:MenuEnter - If we are thinking of un-posting a menu, do not do
   	it if the menu is torn off.
   
   TearOff.c:_XmRestoreTearOffToMenuShell - XSync before we grab the server.
   	Do not XSync while the server is grabbed.  This was a fun one. It
   	seems that if you have the server grabbed in conjuction with
   	DEBUGSOURCES=all something gets bogged down and you get no response
   	if stderr is an xterm.  Re-direct to a file and all was ok.
   	Anyway, with the syncs and grabs altered a bit it seems okay.
CascadeB.c 1.59
   date: 1997/12/11 11:10:12;  author: rwscott;  state: Exp;  lines: +5 -4
   CheckDisarm - RC_PopupPosted == NULL segfault avoidance
CascadeB.c 1.58
   date: 1997/12/07 17:50:15;  author: rwscott;  state: Exp;  lines: +26 -2
   CheckDisarm - If a cascade button is close to the right edge of the screen
   	its submenu will be posted to the left of the cascade button instead
   	of the right.  In this case leaving the left edge of the cascade button
   	should leave the menu posted and leaving on the right edge should
   	un-post the menu, just the opposite of the normal case. So in this
   	special case let's add the width of the submenu to the x value of
   	the event, thus allowing a leave event with an x of less than 0 to
   	be okay. (testing done with rowcolumn/test17)


CascadeBG.c Current rev 1.74 Last Release 1.60
CascadeBG.c 1.74
   date: 1998/03/13 23:07:15;  author: helden;  state: Exp;  lines: +9 -4
   Edge detection tested against 0 rather than XtX/XtY. This fixes unposting
   submenus when leaving its CBG at the top edge.
   
   Added FIX ME: edge detection is wrong when the menu is posted to the
   left of the CBG: we should test for the right edge.
CascadeBG.c 1.73
   date: 1998/03/05 16:29:05;  author: rwscott;  state: Exp;  lines: +10 -7
   Just say NO to gadgets.
   
   In check disarm we were checking to see if the event y value was greater
   than the widget height.  This works for widgets but not for gadgets, since
   the event is relative to the parent of the gadget.  To tell if we left
   the bottom of a gadget the event must be greater than the XtY + XtHeight.
   
   This fixes the into the menu too fast problem in Mosaic.
CascadeBG.c 1.72
   date: 1998/03/01 23:03:16;  author: rwscott;  state: Exp;  lines: +20 -272
   CascadeB[G].c - general cleanup
   
   MenuUtil.c:_XmRC_GadgetTraverseLeft() - It seems that the event that causes
   	this can trigger this more than once.  Protect it with
   	_XmIsEventUnique/_XmRecordEvent.  This is where the strange behaviour
   	of mgdiff's menus during keyboard traversal was coming from.
CascadeBG.c 1.71
   date: 1998/02/28 18:41:56;  author: rwscott;  state: Exp;  lines: +154 -20
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
CascadeBG.c 1.70
   date: 1998/02/27 22:23:23;  author: rwscott;  state: Exp;  lines: +12 -2
   Get rid of the FixOptionMenu calls.  This is replaced by the RC_MenuProc
   XmMENU_SUBMENU which does essentially the same thing except that it is
   now under the control of RC.
CascadeBG.c 1.69
   date: 1998/02/27 13:28:57;  author: rwscott;  state: Exp;  lines: +6 -3
   CascadeBG.c:ArmAndActivate() - currently I use an XmARM_EVENT to show the
   	button as armed. This however sets DragMode to True, so now reset
   	drag mode after the arm.  This will not be a problem when the
   	LabelMenuProcs get written for CascadeBG.
   
   MenuUtil.c:_XmMenuNextItem() - when searching for a valid control just use
   	XmIsTraversable(), it takes care of all of the other cases.
   
   MenuUtil.c:_XmMenuPrevItem() - see above
   
   MenuUtil.c:_XmMenuDisarmItem() - an XmLEAVE_EVENT to a gadget will only draw
   	the gadget un-armed if drag mode is on, therefore force the drag mode
   	to the value needed.  Again, this will not be necessary when the
   	LabelMenuProcs have been written for the Gadget buttons.
   
   RowColumn.c: Disarm the active child during a MENU_SHELL_POPDOWN
CascadeBG.c 1.68
   date: 1998/02/22 21:42:20;  author: rwscott;  state: Exp;  lines: +20 -9
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
CascadeBG.c 1.67
   date: 1998/02/22 14:41:57;  author: rwscott;  state: Exp;  lines: +6 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
CascadeBG.c 1.66
   date: 1998/02/22 04:42:15;  author: rwscott;  state: Exp;  lines: +10 -2
   Mainly comments as to what is going to be changing wrt the menu system.
   Basicly the way the label menu procs are used right now is wrong.  A label
   does not know if a particular button press is the correct button, this is a
   job for RowColumn, the official menu widget. The same is true for un-posting
   menus.  The label menu procs should be used by Label subclasses that can be
   in a menu system.  Through these procs the RowColumn can arm/disarm the
   controls without having to know the details of the control.
   
   So, what does all this mean.  The current contents of the Label[G] menu procs
   will be moved to RowColumn menu procs.  Label[G] menu procs will be written
   for each of the controls that can be in a menu. After that, nothing should
   care, or even know, about private/public menu shells.  All of this should
   be the responsibility of the routines in MenuShell.
   
   If anyone disagrees, now is the time to speak!
CascadeBG.c 1.65
   date: 1998/02/21 01:50:09;  author: rwscott;  state: Exp;  lines: +14 -2
   With this keyboard traversal of menus should be possible. Feedback welcomed!
   
   CascadeB[G].c:ArmAndActivate() - If we post a submenu from a cascade button
   	in a menubar arm the first item in the menu. (Needs to be smarter
   	and arm the first active menu control)
   
   RowColumn.c - change the default radio behaviour back to False. This is wrong
   	according to misc/test16 but until we deal with it in other places
   	it messes up a bunch of toggle buttons in menus. See mgdiff->options
   	for an example.
   
   MenuUtil.c - Write all of the menu traversal handlers.....
   
   ToggleBG.c:[Enter|Leave]Window() - Do not insist on being in DragMode since
   	during keyboard traversal we are not.
CascadeBG.c 1.64
   date: 1998/02/17 13:31:49;  author: rwscott;  state: Exp;  lines: +6 -2
   First cut at keyboard traversal of menus.
   
   CascadeB[G].c:_XmCBMenuBarDoSelect - If we post a submenu then also arm the
   	first item.
   CascadeB[G].c:_XmCBMenuBarSelect - set MGR_ActiveChild for the parent
   
   MenuUtil.c - write a MenuTraversalHandler (A bit of a mess right now)
   
   PushB[G].c - set MGR_ActiveChild when Armed
   
   RowColumn.c - Install the traversal translations on MENU_BAR's.
CascadeBG.c 1.63
   date: 1998/02/15 22:06:26;  author: rwscott;  state: Exp;  lines: +18 -25
   Small tweaks to the class structure to make it like misc/test16 output.
CascadeBG.c 1.62
   date: 1998/02/07 01:33:30;  author: rwscott;  state: Exp;  lines: +3 -3
   CheckDisarm - We were checking if we left the bottom by y > XtY(w) + XtHeight(w)
   	This meant that if you left slow enough the leave event would
   	actually have y = XtY(w) + XtHeight(w) and we did not think we left.
   	Changed it to >= and the Mosaic menus are once again happy.
CascadeBG.c 1.61
   date: 1998/01/28 20:12:32;  author: u27113;  state: Exp;  lines: +3 -3
   test/Xm/*/Makefile.am : be able to build with 2.0 library as well.
   
   working.html : add reference to BRL/CAD 4.4 which is reported to work.
   
   lib/Xm/(Gadgets) : one pixel sensitivity fixes by Gilles Seguin.
   	+ a new test in test/Xm/arrowbg for it.
   
   CURRENT_NOTES : refer to Xinvest as a demo for 2.0 PanedWindow.
   
   Paned* : the year hasn't been 1995 for a long time. Copyright changed.


Command.c Current rev 1.9 Last Release 1.8
Command.c 1.9
   date: 1998/02/22 01:00:25;  author: rwscott;  state: Exp;  lines: +8 -4
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


DebugUtil.c Current rev 1.25 Last Release 1.21
DebugUtil.c 1.25
   date: 1998/03/07 01:10:21;  author: rwscott;  state: Exp;  lines: +7 -6
   Okay, with this nedit seems fine _IFF_ run under LessTif's mwm. If run from
   fvwm everything seems fine _except_ you cannot enter text.  Pretty lame for
   an editor I know but I cannot figure out what the difference is.
   
   If only I had a man page for mwm maybe I would switch :)
DebugUtil.c 1.24
   date: 1998/03/06 22:55:49;  author: rwscott;  state: Exp;  lines: +73 -2
   Manager.c:_XmAcceleratorHandler - add UngrabKeyboard/UngrabPointer calls in
   	here since we get here as the result of an XtGrabKey.
   
   
   One of the problems with accelerators is that we install the XtGrabKey to
   get notification of the event.  When this notification happens the server
   generates a FocusOut event. We pick this up in _XmTrackShellFocus but are
   ignoring the mode of NotifyGrab.  Similarly when we now ungrab we pick this
   up but again are ignoring the mode of NotifyUngrab.  Somewhere in these 2
   focus events we have to save where the focus was before the grab and then
   put it back after the grab.
   
   Any help gratiously accepted.
   
   		Rick
DebugUtil.c 1.23
   date: 1998/02/22 01:00:26;  author: rwscott;  state: Exp;  lines: +25 -2
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
DebugUtil.c 1.22
   date: 1997/12/12 20:01:41;  author: rwscott;  state: Exp;  lines: +6 -2
   add numColumns to print arg list


DefaultProcs.c Current rev 1.9 Last Release 1.5
DefaultProcs.c 1.9
   date: 1997/08/25 17:40:19;  author: miers;  state: dead;  lines: +2 -2
   Woohoo, we get to get rid of a file.
   
   Two things in this patch.
   
   1) Get Thot's scrollbars to match the background like they should.
   
   2) Move all widget default procs from DefaultProcs.c into the widgets
   themselves.  This allows us to get rid of DefaultProcs.c.
   
   Updated the relevant makefiles to reflect this.
DefaultProcs.c 1.8
   date: 1997/08/18 18:49:27;  author: miers;  state: Exp;  lines: +3 -4
   DefaultProcs: Snuck a traversalOn test in ScrollBar defaults that didn't
   work.  Scales still present a traversal problem.
   
   MessageB.c: Add code into initialize for TEMPLATE checking.
   
   PushB.c: Add NULL event checking from JAC.
   
   Visual.c: Add 1 deep caching for colors from JAC.
   
   XmString.c: Change DrawUnderline to use current_y + line_descent rather
   than current_y + 1 for the underline.  This looks more like Motif.
DefaultProcs.c 1.7
   date: 1997/08/15 23:04:45;  author: miers;  state: Exp;  lines: +4 -3
   Remove extra FIXME's from the CoreClassExtRec(s).  This reduces the list
   to a manageable size (401:)
DefaultProcs.c 1.6
   date: 1997/07/10 01:59:35;  author: miers;  state: Exp;  lines: +100 -42
   Indent fun.
   
   Oh, there's one other thing.  While I'm doing this, I've added a macro
   DEBUGOUT(x) into the DebugUtil.h file.  This macro is empty for
   LESSTIF_PRODUCTION, or expands to its arg when not LESSTIF_PRODUCTION.
   I'm using it as follows:
   
   	DEBUGOUT(XdbDebug(__FILE__, w, "foo was here."));
   
   So that when LESSTIF_PRODUCTION, no debug statement is there.  Danny,
   you may want to change this (maybe another preprocessor flag in
   DebugUtil.h?).
DefaultProcs.c 1.4
   date: 1997/06/04 02:51:06;  author: miers;  state: Exp;  lines: +2 -44
   DefaultProcs.c: Remove dead calls.
   
   GeoUtils.c: Slight rework of _XmGeoLoadValues.
   
   RCUtils.c, RowColumn.c: Real close to there.  I've identified the problem
   areas, but I can't seem to find the combination that gets xmcd and
   xephem both to work.
DefaultProcs.c 1.3
   date: 1997/04/14 06:06:18;  author: u27113;  state: Exp;  lines: +14 -3
   ScrolledW.c : *finally* got the damned thing figured out, after realizing
   	that the scrollbars were misbehaving, which kept me puzzled for weeks.
   
   DebugUtil.c : add function XdbMenuType2String
   DefaultProcs.c : change default for traversing scrollbars in a
   	scrolledwindow. (Traverse when XmAUTOMATIC).
   Primitive.c : add XdbDebug.
   ScrollBar.c : remove test from scrollbar_unhighlight and scrollbar_highlight.
   	Should do Scale stuff via initialisation.
   Traversal.c : add XdbDebug.
DefaultProcs.c 1.2
   date: 1997/03/16 14:17:47;  author: helden;  state: Exp;  lines: +3 -3
   ScrollBar.c:
   	Make it picky again about initial values.
   
   DefaultProcs.c:
   	Motif docs says scrollbar is traversable unless
   	parent is a ScrolledWindow.
   
   RowColumn.c:
   	First shot at implementing menuProcedures. (Not yet used :)
DefaultProcs.c 1.1
   date: 1997/02/20 02:48:09;  author: miers;  state: Exp;
   It's as bad as it looks;)
   
   I HIGHLY recommend to core people that you blow away your source tree, and
   checkout with the prune (-P) option to get rid of empty directories, until
   or unless the empty directories are removed from the repository.
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/Desktop.c,v
   Working file: Desktop.c
   head: 1.4
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.3
   	release_0_81: 1.3
   	release_0_80public: 1.1
   	release_0_80: 1.1
   	release_0_79: 1.1
   	release_0_78: 1.1
   keyword substitution: kv
   total revisions: 4;	selected revisions: 2
   description:
DefaultProcs.c 1.4
   date: 1998/02/22 01:00:27;  author: rwscott;  state: Exp;  lines: +13 -5
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
DefaultProcs.c 1.3
   date: 1997/07/12 18:36:55;  author: miers;  state: Exp;  lines: +7 -7
   Indenting done -- whew.
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/Dest.c,v
   Working file: Dest.c
   head: 1.1
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.1
   	release_0_81: 1.1
   	release_0_80public: 1.1
   	release_0_80: 1.1
   	release_0_79: 1.1
   	release_0_78: 1.1
   keyword substitution: kv
   total revisions: 1;	selected revisions: 1
   description:
DefaultProcs.c 1.1
   date: 1997/02/20 02:48:11;  author: miers;  state: Exp;
   It's as bad as it looks;)
   
   I HIGHLY recommend to core people that you blow away your source tree, and
   checkout with the prune (-P) option to get rid of empty directories, until
   or unless the empty directories are removed from the repository.
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/DialogS.c,v
   Working file: DialogS.c
   head: 1.9
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.9
   	release_0_81: 1.7
   	release_0_80public: 1.3
   	release_0_80: 1.3
   	release_0_79: 1.1
   	release_0_78: 1.1
   keyword substitution: kv
   total revisions: 9;	selected revisions: 1
   description:
DefaultProcs.c 1.9
   date: 1997/11/07 01:51:38;  author: miers;  state: Exp;  lines: +7 -7
   Change the InitialPlacement to be dependent on whether or not the DialogS
   has an initial position of 0,0.  This still probably isn't right.
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/Display.c,v
   Working file: Display.c
   head: 1.11
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.9
   	release_0_81: 1.8
   	release_0_80public: 1.6
   	release_0_80: 1.6
   	release_0_79: 1.6
   	release_0_78: 1.6
   keyword substitution: kv
   total revisions: 11;	selected revisions: 3
   description:
DefaultProcs.c 1.11
   date: 1998/02/22 01:00:28;  author: rwscott;  state: Exp;  lines: +13 -9
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
DefaultProcs.c 1.10
   date: 1998/02/04 20:41:04;  author: u27113;  state: Exp;  lines: +13 -2
   FAQ : add question about LessTif 0.82 which thinks it's 0.81.
   Display.c : XdbDebug change, also NULL a pointer after freeing it.
   MenuShell.c : When using an accelerator, we XtUnmanageChild'd something
   	without a reason for it. This caused all kinds of strange things
   	to get called for no reason. Fixed.
   Draw.c : Found yet another reason for a loop overrun which caused a crash.
   	In XmeDrawArrow; happened in xmgr.
DefaultProcs.c 1.9
   date: 1997/11/11 14:46:22;  author: rwscott;  state: Exp;  lines: +3 -3
   More default resource sync'ing
   
   
   
   PushBG.c - change highlightthickness to the CallProc
            - change shadowthickness to the CallProc
   
   CascadeBG.c - change highlightthickness to the CallProc
               - change shadowthickness to the CallProc
   
   Gadget.c - change highlightthickness to the CallProc
   
   Display.c - change class of defaultVirtualBindings from String to
   	DefaultVirutalBindings.
   
   TextF.c - fix up the default selectionArray resource
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/DragBS.c,v
   Working file: DragBS.c
   head: 1.7
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.7
   	release_0_81: 1.7
   	release_0_80public: 1.5
   	release_0_80: 1.5
   	release_0_79: 1.5
   	release_0_78: 1.5
   keyword substitution: kv
   total revisions: 7;	selected revisions: 1
   description:
DefaultProcs.c 1.7
   date: 1997/08/25 23:34:29;  author: miers;  state: Exp;  lines: +4 -4
   Some fixes for Insure++ warnings.
   
   Also, the mad indenter hit ScrollBar.  PvH, if you're still working on
   this, just use the last version and overwrite when you're done.
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/DragC.c,v
   Working file: DragC.c
   head: 1.18
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.17
   	release_0_81: 1.16
   	release_0_80public: 1.13
   	release_0_80: 1.13
   	release_0_79: 1.13
   	release_0_78: 1.13
   keyword substitution: kv
   total revisions: 18;	selected revisions: 2
   description:
DefaultProcs.c 1.18
   date: 1998/02/22 01:00:29;  author: rwscott;  state: Exp;  lines: +12 -8
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
DefaultProcs.c 1.17
   date: 1997/11/05 04:39:48;  author: rwscott;  state: Exp;  lines: +4 -4
   It looks worse than it really is!!
   
   Just re-ordering the action strings to make the misc/test16 diffs easier
   to spot which action are missing from the default Class records.
   =============================================================================
   
   RCS file: /cvsroot/hungry/lesstif/lib/Xm/DragDrop.c,v
   Working file: DragDrop.c
   head: 1.5
   branch:
   locks: strict
   access list:
   symbolic names:
   	release_0_82: 1.5
   	release_0_81: 1.5
   	release_0_80public: 1.2
   	release_0_80: 1.2
   	release_0_79: 1.2
   	release_0_78: 1.2
   keyword substitution: kv
   total revisions: 5;	selected revisions: 1
   description:


DragOverS.c Current rev 1.8 Last Release 1.7
DragOverS.c 1.8
   date: 1998/02/22 01:00:30;  author: rwscott;  state: Exp;  lines: +7 -3
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


DrawingArea.c Current rev 1.20 Last Release 1.19
DrawingArea.c 1.20
   date: 1997/11/21 18:01:08;  author: miers;  state: Exp;  lines: +5 -5
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.


DrawnB.c Current rev 1.23 Last Release 1.20
DrawnB.c 1.23
   date: 1998/02/22 01:00:31;  author: rwscott;  state: Exp;  lines: +6 -2
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
DrawnB.c 1.22
   date: 1998/02/07 15:20:22;  author: rwscott;  state: Exp;  lines: +31 -3
   DrawnB.c - add some debug stuff
   Form.c - A bit of a hack coming up....
   
   Add the realize method back into Form.
   
      Motif inherits the realize method for Form but, since we are not
      participating in all of the GeoUtils stuff for Form this is necessary.
      If we inherit this from BulletinBoard we end up enforcing margins and
      other stuff that should not be done.  Using the GeoUtils would be one
      way to fix this but this is _much_ simpler at this stage!
   
      This showed up in xdir.  The llnlxdirButton in the top right beside
      the menubar was being placed wrong.  Form was calculating a y value
      of -2, because of the topOffset, and BulletinBoard was then enforcing
      a margin of 0.
DrawnB.c 1.21
   date: 1997/12/26 21:39:24;  author: u27113;  state: Exp;  lines: +38 -4
   Add a trait.


DropSMgr.c Current rev 1.15 Last Release 1.14
DropSMgr.c 1.15
   date: 1998/02/22 01:00:32;  author: rwscott;  state: Exp;  lines: +10 -6
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


DropTrans.c Current rev 1.8 Last Release 1.7
DropTrans.c 1.8
   date: 1998/02/22 01:00:33;  author: rwscott;  state: Exp;  lines: +12 -6
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


FileSB.c Current rev 1.24 Last Release 1.21
FileSB.c 1.24
   date: 1998/02/22 14:41:58;  author: rwscott;  state: Exp;  lines: +3 -3
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
FileSB.c 1.23
   date: 1998/02/22 01:00:34;  author: rwscott;  state: Exp;  lines: +42 -8
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
FileSB.c 1.22
   date: 1997/12/13 18:32:50;  author: rwscott;  state: Exp;  lines: +17 -3
   _XmFsbButton - the dir, mask, and pattern were being copied into the cbs but,
   	the widget instance variables were the ones being freed at the end of
   	the routine!
   
   This is the main reason for the segfault in hvplot.  The other was the list
   default action call parentProcess (which was fixed a while ago).


FontList.c Current rev 1.10 Last Release 1.7
FontList.c 1.10
   date: 1998/03/13 22:42:13;  author: u27113;  state: Exp;  lines: +3 -3
   Vendor.c : now it can work for 2.0 too.
   
   FontList.c : warning removed.
   
   lib/Xm-2.0/Makefile.am : pick up the lib/Xm version instead of lib/Xm-2.0
   	of Vendor.c
FontList.c 1.9
   date: 1998/03/13 21:44:42;  author: u27113;  state: Exp;  lines: +3 -2
   Fix memory leak as indicated on the list.
FontList.c 1.8
   date: 1997/12/28 21:34:50;  author: u27113;  state: Exp;  lines: +8 -2
   Remove leading and trailing " in font lists.
   Also modify the macro that includes nonstandard converters,
   and build it into the configuration.
   
   Configuration: also add the test Makefiles.


Form.c Current rev 1.106 Last Release 1.103
Form.c 1.106
   date: 1998/02/07 15:20:23;  author: rwscott;  state: Exp;  lines: +30 -3
   DrawnB.c - add some debug stuff
   Form.c - A bit of a hack coming up....
   
   Add the realize method back into Form.
   
      Motif inherits the realize method for Form but, since we are not
      participating in all of the GeoUtils stuff for Form this is necessary.
      If we inherit this from BulletinBoard we end up enforcing margins and
      other stuff that should not be done.  Using the GeoUtils would be one
      way to fix this but this is _much_ simpler at this stage!
   
      This showed up in xdir.  The llnlxdirButton in the top right beside
      the menubar was being placed wrong.  Form was calculating a y value
      of -2, because of the topOffset, and BulletinBoard was then enforcing
      a margin of 0.
Form.c 1.105
   date: 1998/01/24 15:24:05;  author: rwscott;  state: Exp;  lines: +30 -317
   Clean out some of the code that has been dead for many many months
Form.c 1.104
   date: 1998/01/04 18:16:42;  author: rwscott;  state: Exp;  lines: +51 -11
   All of the XmATTACH_WIDGET/XmATTACH_OPPOSITE_WIDGET
   
   Now that the geometry management is better than it was in Feb 1997, if we get
   to this point and the attached-to widget is NULL then change the attachment
   to XmATTACH_FORM whether the form is realized or not. It seems that this was
   added mainly for mgdiff, which seems to be fine without it now.
   
   form/test32 based on an app from Bill Powers <wepprop@bigfoot.com>


Frame.c Current rev 1.34 Last Release 1.33
Frame.c 1.34
   date: 1998/02/22 01:00:35;  author: rwscott;  state: Exp;  lines: +16 -5
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


Gadget.c Current rev 1.11 Last Release 1.7
Gadget.c 1.11
   date: 1998/02/22 01:00:36;  author: rwscott;  state: Exp;  lines: +11 -7
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
Gadget.c 1.10
   date: 1997/12/26 16:06:32;  author: u27113;  state: Exp;  lines: +3 -3
   INSTALL: some newer comments.
   
   PushB.c, PushBG.c : add trait.
   	It's been bothering me for a while that XmText lives in both
   	directories with only simple differences, this is a nightmare.
   
   	I'd like to see if we can keep SIMPLE 2.0 stuff in the 1.2 tree.
   	Barring a veto from you guys off course.
   
   	Currently my feeling is this : if we can get away with just
   	adding traits stuff by #ifdefs, do it in the 1.2 tree.
   
   Gadget.c : small fix to SetValues.
   
   Notebook.c : add some code. Not functional yet.
   Trait.c : small fix, don't really understand the problem.
   
   ActivatableT.h is a new trait header file.
Gadget.c 1.9
   date: 1997/11/21 18:01:09;  author: miers;  state: Exp;  lines: +6 -6
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.
Gadget.c 1.8
   date: 1997/11/21 04:32:20;  author: miers;  state: Exp;  lines: +3 -2
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


GadgetUtil.c Current rev 1.6 Last Release 1.4
GadgetUtil.c 1.6
   date: 1998/03/09 21:13:59;  author: rwscott;  state: Exp;  lines: +3 -3
   A DEBUG statement in _XmDispatchGadgetInput was causing xmbase-grok to
   segfault.
GadgetUtil.c 1.5
   date: 1998/01/28 20:12:33;  author: u27113;  state: Exp;  lines: +4 -4
   test/Xm/*/Makefile.am : be able to build with 2.0 library as well.
   
   working.html : add reference to BRL/CAD 4.4 which is reported to work.
   
   lib/Xm/(Gadgets) : one pixel sensitivity fixes by Gilles Seguin.
   	+ a new test in test/Xm/arrowbg for it.
   
   CURRENT_NOTES : refer to Xinvest as a demo for 2.0 PanedWindow.
   
   Paned* : the year hasn't been 1995 for a long time. Copyright changed.


GeoUtils.c Current rev 1.18 Last Release 1.16
GeoUtils.c 1.18
   date: 1997/12/13 22:27:04;  author: rwscott;  state: Exp;  lines: +23 -2
   GeoUtils.c:_XmMenuBarFix - Add in a GET_PREFERRED_SIZE action to query the
   	preferred size of the menubar.
   
   RCUtils.c:_XmRCPreferredSize - We were simply returning if the RC had no
   	managed children.  This results in the RC remaining its current size.
   	However if we have an RC with a bunch of kids and then unmanage them
   	all, we want the RC to shrink. Therefore even if we have no managed
   	children go through the whole layout deal.
   
   RCUtils.c:_XmRCAdjustSize - ditto
   
   This is all in aid of filesb/test7.  The exact behaviour needs to be compared
   to Motif but hey, I do not have Motif!
GeoUtils.c 1.17
   date: 1997/12/05 23:08:01;  author: u27113;  state: Exp;  lines: +93 -6
   Add a few files to be able to configure the tests too.
   Automake, autoconf should be run nightly on test/* .
   I'll handle that next week.
   
   Futher: a bug fix for Steven Danz's problem with bulletinboard.
   Also added IPE to the list of working apps, fixed a URL too.


ImageCache.c Current rev 1.9 Last Release 1.8
ImageCache.c 1.9
   date: 1998/01/06 23:51:48;  author: miers;  state: Exp;  lines: +72 -27
   Add patches from Paul Flinders for Xpm handling of pixmaps.


LTCvt.c Current rev 1.4 Last Release 1.2
LTCvt.c 1.4
   date: 1997/12/28 21:34:51;  author: u27113;  state: Exp;  lines: +5 -5
   Remove leading and trailing " in font lists.
   Also modify the macro that includes nonstandard converters,
   and build it into the configuration.
   
   Configuration: also add the test Makefiles.
LTCvt.c 1.3
   date: 1997/11/21 04:32:21;  author: miers;  state: Exp;  lines: +9 -2
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


LTEditres.c Current rev 1.6 Last Release 1.1
LTEditres.c 1.6
   date: 1997/08/19 19:29:08;  author: miers;  state: dead;  lines: +0 -0
   More code reorg.
   
   1) Moved all the Xme functions to the 2.0 tree.  Something needs to be
   done about the headers, though.
   
   2) If LESSTIF_PRODUCTION is defined, then the Editres handler and the
      pixmap extensions aren't built.  I'd like to move these to another
      place (e.g., extensions/) but it's so much trouble to hack configure
      that I'm putting it off.
   
   3) Add an Editres for R5.
LTEditres.c 1.5
   date: 1997/07/26 20:22:09;  author: miers;  state: Exp;  lines: +1 -1
   DialogS.c: We seem to need the XtUnmapWidget (nedit->Open->Ok, without
   selecting anything).  However, move it to after the XtPopdown call.
   
   Form.c: Added a #define, NO_QUERY_GEO (currently #undef'ed) that replaces
   the XtQueryGeometry call with retrieval of w/h/bw.  This mostly works,
   except in the case where the form changes (see test15,
   xephem->Earth View->Spherical); something more is needed before the XtQuery
   can go for good.  Rick, you may want to take a look, you know this puppy
   better than me.  Maybe this could be where InitialWidth/Height comes into
   play?  Dunno.
   
   LTEditres.c, Label.c, LabelG.c, ResConvert.c: Warning removal.
   
   Vendor.c: Cleanup some of the dead code.
LTEditres.c 1.4
   date: 1997/07/11 02:30:01;  author: miers;  state: Exp;  lines: +1 -0
   Alter DebugUtil so it doesn't need any Motif headers for use.
   For LTEditres.
LTEditres.c 1.3
   date: 1997/07/11 02:22:17;  author: miers;  state: Exp;  lines: +985 -887
   Indent.
LTEditres.c 1.2
   date: 1997/07/08 18:41:49;  author: u27113;  state: Exp;  lines: +221 -0
   lib/Xm/LTEditres.c, lib/Xm/ResConvert.c : Changes to add EditRes GET behaviour,
   	including a couple of resource converters (*-to-string), including
   	int-to-string, XmString-to-string. Check out e.g. labelString on any
   	XmLabel subclass.
   lib/Xm/TextOut.c : these fixes should make the thing more stable.
   	Fixed a number of PASTENDPOS bugs.
   test/Xm/form/test6.c : expanded test.


LTXpm.c Current rev 1.3 Last Release 1.2
LTXpm.c 1.3
   date: 1998/02/09 15:09:11;  author: u27113;  state: Exp;  lines: +0 -3
   ../commit-msg


Label.c Current rev 1.58 Last Release 1.45
Label.c 1.58
   date: 1998/03/08 18:43:05;  author: rwscott;  state: Exp;  lines: +3 -3
   Fixes from "Alexander Mai" <st002279@hrzpub.tu-darmstadt.de>
   
   I just turned -Wall back on for myself so things like this should not so
   easily slip by. It must have got turned off in the automake upgrade.
Label.c 1.57
   date: 1998/03/03 21:58:50;  author: rwscott;  state: Exp;  lines: +3 -258
   Get rid of the remnants of the label menu procs
Label.c 1.56
   date: 1998/02/28 18:41:57;  author: rwscott;  state: Exp;  lines: +7 -3
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
Label.c 1.55
   date: 1998/02/26 03:18:00;  author: miers;  state: Exp;  lines: +5 -2
   Rick, something that may help a bit.  Traversal in a menu also depends on
   traversalOn (or XmIsTraversable()), which was demonstrated by nedit's "fake"
   menu items.
   
   Label.c, LabelG.c:  Does anyone know why traversalOn was being set to FALSE
   for items in a menu?  Changed to highlightOnEnter set to false.
   
   MenuUtil.c: Check for not only a) not a Separator, and b) is XtSensitive(),
   but include c) XmIsTraversable().  This required a change to RowColumn.
   
   RowColumn.c: in widgetNavigable(), check for XtIsSensitive() and
   MGR_TraversalOn() and a) is WORK_AREA or OPTION_MENU, or b) is PULLDOWN or
   POPUP and !inDragMode, or c) is MENU_BAR and !inDragMode and PopupPosted.
   Any of those conditions are a navigable RC.
   
   Finally, you can probably lose (a) from MenuUtil, as a separator should never
   be navigable in a menu.  Also, a note to Chris: what is Netscape going to do
   about the dependencies on undocumented Motif data structures and functions
   in Communicator?  (Netscape is set to release the source to Communicator,
   if you didn't know: check out http://www.mozilla.org).  Somebody was asking
   on the list today about undocumented functions that Communicator uses
   (_XmDSIAddChild() et alia).  Will you have to have Motif source to contribute
   to Communicator?  Or will Motif DnD FINALLY be documented for the masses?
Label.c 1.54
   date: 1998/02/22 21:42:21;  author: rwscott;  state: Exp;  lines: +14 -3
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
Label.c 1.53
   date: 1998/02/22 14:41:59;  author: rwscott;  state: Exp;  lines: +9 -3
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
Label.c 1.52
   date: 1998/02/22 04:42:16;  author: rwscott;  state: Exp;  lines: +6 -2
   Mainly comments as to what is going to be changing wrt the menu system.
   Basicly the way the label menu procs are used right now is wrong.  A label
   does not know if a particular button press is the correct button, this is a
   job for RowColumn, the official menu widget. The same is true for un-posting
   menus.  The label menu procs should be used by Label subclasses that can be
   in a menu system.  Through these procs the RowColumn can arm/disarm the
   controls without having to know the details of the control.
   
   So, what does all this mean.  The current contents of the Label[G] menu procs
   will be moved to RowColumn menu procs.  Label[G] menu procs will be written
   for each of the controls that can be in a menu. After that, nothing should
   care, or even know, about private/public menu shells.  All of this should
   be the responsibility of the routines in MenuShell.
   
   If anyone disagrees, now is the time to speak!
Label.c 1.51
   date: 1998/02/20 15:11:02;  author: rwscott;  state: Exp;  lines: +11 -8
   Label.c - Move some more of the actions over to RowColumn (see misc/test16)
   
   RowColumn - define the actions that used to be in Label
   	bring the class structure and default resources more in-line with
   	Motif (see misc/test16)
Label.c 1.50
   date: 1998/02/20 05:45:21;  author: rwscott;  state: Exp;  lines: +19 -4
   Label.c - get rid of the FocusIn action this is actually in RowColumn
   	  Label still has a few more that need to move to RowColumn
   
   Manager.c:_XmAcceleratorHandler() - When an action proc is called directly
   	you must pass a pointer to the num_params, not NULL
   
   RowColumn - define the FocusIn action proc that was in Label
   
   AnythingElse - Debug stuff
Label.c 1.49
   date: 1998/02/17 21:11:53;  author: rwscott;  state: Exp;  lines: +4 -3
   Use the menu translations in a MENU_BAR also
Label.c 1.48
   date: 1997/12/14 14:45:50;  author: rwscott;  state: Exp;  lines: +8 -2
   Label.c:label_menu_procs - case XmMENU_SHELL_POPDOWN -  If we have a menubar
   	with button1 and button2 and a tearoff is posted for button1 and we
   	click in button2 this routine gets called to popdown the menu for
   	button1.  Therefore if the menu to popdown is not in a menushell
   	leave it alone.
   
   MenuShell.c:MenuShellPopdownDone - If the top level widget is not a menushell
   	it must be a tearoff. In this case popdown everyone under the toplevel.
   
   TearOff.c:_XmTearOffInitiate - Preserve the value of RC_PopupPosted around the
   	call to MenuShellPopdownDone. Same as preserving the value of
   	RC_CascadeBtn.
   
   ToggleB.c:ButtonDown - Like most other places in this file when we set the
   	value for TB_IndicatorSet also set the value of TB_VisualSet.
   
   
   All of this was with tearoff/test2
Label.c 1.47
   date: 1997/11/25 14:34:34;  author: rwscott;  state: Exp;  lines: +2 -14
   initialize: Motif does _not_ interpret \n when using the widget name for
   	the labelString! Back out yesterday's change.
   
   Shame on me, I should have checked this out first.
Label.c 1.46
   date: 1997/11/24 21:36:32;  author: rwscott;  state: Exp;  lines: +14 -2
   initialize: apparently a \n in the widget name will be a new line in the
   	label if the the labelString resource is not set.  Change the
   	string create call to one that honors \n.


LabelG.c Current rev 1.51 Last Release 1.40
LabelG.c 1.51
   date: 1998/03/03 21:58:51;  author: rwscott;  state: Exp;  lines: +3 -179
   Get rid of the remnants of the label menu procs
LabelG.c 1.50
   date: 1998/02/28 18:41:58;  author: rwscott;  state: Exp;  lines: +8 -3
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
LabelG.c 1.49
   date: 1998/02/26 03:18:01;  author: miers;  state: Exp;  lines: +5 -2
   Rick, something that may help a bit.  Traversal in a menu also depends on
   traversalOn (or XmIsTraversable()), which was demonstrated by nedit's "fake"
   menu items.
   
   Label.c, LabelG.c:  Does anyone know why traversalOn was being set to FALSE
   for items in a menu?  Changed to highlightOnEnter set to false.
   
   MenuUtil.c: Check for not only a) not a Separator, and b) is XtSensitive(),
   but include c) XmIsTraversable().  This required a change to RowColumn.
   
   RowColumn.c: in widgetNavigable(), check for XtIsSensitive() and
   MGR_TraversalOn() and a) is WORK_AREA or OPTION_MENU, or b) is PULLDOWN or
   POPUP and !inDragMode, or c) is MENU_BAR and !inDragMode and PopupPosted.
   Any of those conditions are a navigable RC.
   
   Finally, you can probably lose (a) from MenuUtil, as a separator should never
   be navigable in a menu.  Also, a note to Chris: what is Netscape going to do
   about the dependencies on undocumented Motif data structures and functions
   in Communicator?  (Netscape is set to release the source to Communicator,
   if you didn't know: check out http://www.mozilla.org).  Somebody was asking
   on the list today about undocumented functions that Communicator uses
   (_XmDSIAddChild() et alia).  Will you have to have Motif source to contribute
   to Communicator?  Or will Motif DnD FINALLY be documented for the masses?
LabelG.c 1.48
   date: 1998/02/22 21:42:22;  author: rwscott;  state: Exp;  lines: +16 -4
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
LabelG.c 1.47
   date: 1998/02/22 14:42:01;  author: rwscott;  state: Exp;  lines: +9 -3
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
LabelG.c 1.46
   date: 1998/02/22 04:42:17;  author: rwscott;  state: Exp;  lines: +7 -3
   Mainly comments as to what is going to be changing wrt the menu system.
   Basicly the way the label menu procs are used right now is wrong.  A label
   does not know if a particular button press is the correct button, this is a
   job for RowColumn, the official menu widget. The same is true for un-posting
   menus.  The label menu procs should be used by Label subclasses that can be
   in a menu system.  Through these procs the RowColumn can arm/disarm the
   controls without having to know the details of the control.
   
   So, what does all this mean.  The current contents of the Label[G] menu procs
   will be moved to RowColumn menu procs.  Label[G] menu procs will be written
   for each of the controls that can be in a menu. After that, nothing should
   care, or even know, about private/public menu shells.  All of this should
   be the responsibility of the routines in MenuShell.
   
   If anyone disagrees, now is the time to speak!
LabelG.c 1.45
   date: 1998/02/22 01:00:37;  author: rwscott;  state: Exp;  lines: +19 -11
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
LabelG.c 1.44
   date: 1998/02/12 20:44:43;  author: rwscott;  state: Exp;  lines: +6 -2
   PushBG.c:set_values - added in a being_destroyed check because xdir was
   	segfaulting after typing in a password during a connect->remote.
   
   LabelG.c:set_values - refresh is needed if the sensitivity changes.
   	This was causing xdir's menu buttons to be shown in the wrong
   	state after a file transfer.
LabelG.c 1.43
   date: 1997/12/23 20:27:53;  author: helden;  state: Exp;  lines: +6 -4
   Submenus were not popped down. (Try Mosaic:Options->Fonts, then Navigate).
   Fixed.
LabelG.c 1.42
   date: 1997/11/25 14:34:36;  author: rwscott;  state: Exp;  lines: +2 -14
   initialize: Motif does _not_ interpret \n when using the widget name for
   	the labelString! Back out yesterday's change.
   
   Shame on me, I should have checked this out first.
LabelG.c 1.41
   date: 1997/11/24 21:36:34;  author: rwscott;  state: Exp;  lines: +14 -2
   initialize: apparently a \n in the widget name will be a new line in the
   	label if the the labelString resource is not set.  Change the
   	string create call to one that honors \n.


List.c Current rev 1.38 Last Release 1.31
List.c 1.38
   date: 1998/02/22 01:00:38;  author: rwscott;  state: Exp;  lines: +7 -5
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
List.c 1.37
   date: 1998/02/12 22:24:28;  author: rwscott;  state: Exp;  lines: +6 -2
   removed the 2 XmUpdateDisplay calls. This stops most of the flashing in ml
   when any of the lists are being changed.
List.c 1.36
   date: 1998/02/06 23:47:10;  author: rwscott;  state: Exp;  lines: +24 -5
   _XmListInvokeCallbacks - If List_LastItem is 0, meaning nothing is selected
   	then set the calldata.item to the List_LastHLItem, if it is not 0,
   	instead of NULL.  This was causing a segfault in ml when selecting
   	a mailbox that is already highlighted
List.c 1.35
   date: 1997/12/14 22:15:27;  author: rwscott;  state: Exp;  lines: +3 -3
   XmListGetMatchPos - Initialize *position_list to NULL not position_list.
   
   Thanks Jon, it probably slipped by last time you submitted it.  It still
   took me a couple of looks before I noticed the difference!
List.c 1.34
   date: 1997/12/12 15:09:39;  author: rwscott;  state: Exp;  lines: +12 -5
   XmListSetBottomItem - This could call _XmListSetTopPos with a position less
   	than 1. This would screw up the list display.  This is the cause of
   	the font selection screw ups in nedit's font selection. Now if the
   	new position is less than 1 we set it equal to 1.
List.c 1.33
   date: 1997/12/11 02:11:07;  author: rwscott;  state: Exp;  lines: +12 -8
   ListBeginSelect - In the SINGLE_SELECT case the last selected item was being
   	de-selected, which set List_LastItem to 0, and then if List_LastItem
   	was not equal to the new position this position was selected. This
   	meant that a list item selection could not be toggled.  We now save
   	the old position and compare that against the new position and select
   	if they are different. (list/test2)
List.c 1.32
   date: 1997/12/05 00:09:13;  author: rwscott;  state: Exp;  lines: +32 -17
   ListDefaultAction - Do not propagate the ACTIVATE to the parent.
   
   ListKbdCancel - Propagate the CANCEL action to the parent.
   ListKbdActivate - Propagate the ACTIVATE action to the parent.
   
   This was messing up double clicks in the FileSB's dirList.


MainW.c Current rev 1.26 Last Release 1.24
MainW.c 1.26
   date: 1998/02/22 01:00:42;  author: rwscott;  state: Exp;  lines: +16 -16
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
MainW.c 1.25
   date: 1997/12/05 02:02:50;  author: rwscott;  state: Exp;  lines: +4 -3
   typo in the CONF macro, XtY(wid) = cg->x changed to cg->y


Makefile.in Current rev 1.15 Last Release 1.13
Makefile.in 1.15
   date: 1997/12/26 21:44:55;  author: u27113;  state: dead;  lines: +0 -0
   Remove files.
Makefile.in 1.14
   date: 1997/12/21 14:16:52;  author: rwscott;  state: Exp;  lines: +327 -198
   This is all with respect to tearoffs.
   
   
   CascadeB.c
   
   	MenuBarEnter - Popdown the old menu only if a menushell (not torn off)
   
   	CascadePopupHandler - make sure the menu is back in its menu shell if
   		it was torn off
   
   	DelayedArm - Do not put a torn off menu back to its menushell here.
   		If the delay never times out then the menu is left in the
   		menu shell and never poped up.
   
   	CheckDisarm - If we have to popdown the menus use popdownEveryone.
   
   MenuShell.c
   
   	change_managed - If there are no managed children we pop down but, we
   	must popdown private shells different from public ones. Same goes for
   	popping up.
   
   	MenuShellPopdownOne - do not restore tear off to its toplevel shell
   	here, it just confuses popdowneveryone.
   
   	MenuShellPopdownEveryone - restore tear offs to their toplevel shells
   	here, after all the menus have been sorted out.
   
   	MenuShellPopupSharedMenuPane - Since we do not use XtPopup for menus
   	anymore we must take care of setting and un-setting of Shell_PoppedUp.
   	Not setting this was messing up <BtnDown> in push button and
   	probably other places (anywhere there was an if (Shell_PoppedUp)).
   
   PushB.c
   
   	Add some debug statements.
   
   RowColumn.c
   
   	DoBtnEventCleanupReplay - Do not call PopdownDone for a torn off menu
   
   	_XmGetActiveTopLevelMenu - Return something usefull for an active
   	tear off.
   
   TearOff.c
   
   	_XmTearOffBtnDownEventHandler - Arm the menu. Something a little
   	strange happens here, see the comments in the source.
   
   	_XmTearOffBtnUpEventHandler - DisArm the menu.
   
   	_XmTearOffInitiate - Get rid of the keyboard and pointer grabs from
   	the previous menu and turn off drag mode.
   
   	_XmAddTearOffEventHandlers - big time guess here! Add a button up
   	handler to the tear off and all of its widget children so we can
   	disarm the menu. Add a button down handler to all of the widget
   	children so we can arm the menu.
   
   	_XmRestoreTearOffToToplevelShell - Do not ungrab things here. The
   	grabs are now taken care of in the event handlers.
   	Do not reposition the shell if an event is not given.  This is due
   	the the MenuShell:change_managed call to put the menu back to the
   	toplevel shell.
   	Make sure the event handlers are in place.
   
   	_XmRestoreTearOffToMenuShell - Time for a little magic here! Ever
   	wonder how Motif keeps a copy of the tear off in the toplevel shell
   	and displays it in the menu at the same time?  Well you just take a
   	copy of the pixels in the toplevel shell before you re-parent the
   	menu and put those pixels into the shell.  Since the menu will have
   	grabs there is no way to interact with it so fake it!
   	I should be able to just set the background pixmap of the shell and
   	have X take care of the copy, stay tuned.
   	Do not unmanage the menu if it is in a private shell, they are always
   	managed.


Manager.c Current rev 1.46 Last Release 1.37
Manager.c 1.46
   date: 1998/03/12 20:26:25;  author: helden;  state: Exp;  lines: +3 -5
   This is a change relative to 1.43:
   
     - Removed XAllowEvents call from _XmAcceleratorHandler (as in 1.44)
   
     - Changed GrabModeSync to GrabModeAsync for both pointer and keyboard
       mode in the XtGrabKey call.
Manager.c 1.45
   date: 1998/03/07 01:10:22;  author: rwscott;  state: Exp;  lines: +2 -8
   Okay, with this nedit seems fine _IFF_ run under LessTif's mwm. If run from
   fvwm everything seems fine _except_ you cannot enter text.  Pretty lame for
   an editor I know but I cannot figure out what the difference is.
   
   If only I had a man page for mwm maybe I would switch :)
Manager.c 1.44
   date: 1998/03/06 22:55:50;  author: rwscott;  state: Exp;  lines: +10 -4
   Manager.c:_XmAcceleratorHandler - add UngrabKeyboard/UngrabPointer calls in
   	here since we get here as the result of an XtGrabKey.
   
   
   One of the problems with accelerators is that we install the XtGrabKey to
   get notification of the event.  When this notification happens the server
   generates a FocusOut event. We pick this up in _XmTrackShellFocus but are
   ignoring the mode of NotifyGrab.  Similarly when we now ungrab we pick this
   up but again are ignoring the mode of NotifyUngrab.  Somewhere in these 2
   focus events we have to save where the focus was before the grab and then
   put it back after the grab.
   
   Any help gratiously accepted.
   
   		Rick
Manager.c 1.43
   date: 1998/02/22 01:00:43;  author: rwscott;  state: Exp;  lines: +6 -4
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
Manager.c 1.42
   date: 1998/02/20 05:45:23;  author: rwscott;  state: Exp;  lines: +6 -5
   Label.c - get rid of the FocusIn action this is actually in RowColumn
   	  Label still has a few more that need to move to RowColumn
   
   Manager.c:_XmAcceleratorHandler() - When an action proc is called directly
   	you must pass a pointer to the num_params, not NULL
   
   RowColumn - define the FocusIn action proc that was in Label
   
   AnythingElse - Debug stuff
Manager.c 1.41
   date: 1998/01/06 00:46:19;  author: miers;  state: Exp;  lines: +3 -2
   configure.in: Change NONSTANDARD_CONVERSIONS to NONSTANDARD_CONVERTERS.
   
   mwm/Makefile.am: There is no such file as mwmlex.h
   
   lib/*/Makefile.am: A bunch of fixes (none to the 1.2 source) for building
   on Solaris.
   
   MapEvent.c, Manager.c: Missing include of <X11/Xfuncs.h> for bzero, bcopy.
Manager.c 1.40
   date: 1997/11/24 18:29:59;  author: miers;  state: Exp;  lines: +28 -4
   Tracking down broken accelerators in mgdiff.  I *think* this fixes them
   (inverted return val in SetLateModifiers, missing 0 case).
Manager.c 1.39
   date: 1997/11/21 18:01:11;  author: miers;  state: Exp;  lines: +7 -7
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.
Manager.c 1.38
   date: 1997/11/21 04:32:22;  author: miers;  state: Exp;  lines: +51 -8
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


MapEvent.c Current rev 1.10 Last Release 1.6
MapEvent.c 1.10
   date: 1998/01/06 00:46:22;  author: miers;  state: Exp;  lines: +3 -2
   configure.in: Change NONSTANDARD_CONVERSIONS to NONSTANDARD_CONVERTERS.
   
   mwm/Makefile.am: There is no such file as mwmlex.h
   
   lib/*/Makefile.am: A bunch of fixes (none to the 1.2 source) for building
   on Solaris.
   
   MapEvent.c, Manager.c: Missing include of <X11/Xfuncs.h> for bzero, bcopy.
MapEvent.c 1.9
   date: 1997/11/24 18:30:01;  author: miers;  state: Exp;  lines: +11 -5
   Tracking down broken accelerators in mgdiff.  I *think* this fixes them
   (inverted return val in SetLateModifiers, missing 0 case).
MapEvent.c 1.8
   date: 1997/11/21 19:42:55;  author: miers;  state: Exp;  lines: +76 -49
   linux-shared.mk: add the patch from Debian.
   
   MapEvent.c: Add Andreas Zeller's patch for missing modifiers.
MapEvent.c 1.7
   date: 1997/11/21 04:32:24;  author: miers;  state: Exp;  lines: +6 -2
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


MenuShell.c Current rev 1.65 Last Release 1.52
MenuShell.c 1.65
   date: 1998/03/09 22:32:36;  author: u27113;  state: Exp;  lines: +6 -5
   scripts/FreeBSD/Makefile.am
   	Replace the 0.81 version number in the file by something more
   	appropriate.
   
   lib/Xm/MenuShell.c
   	Finally found the cause of my ddd problem.
   	if (VAR(old) == VAR(new)) in set_values should not be == but !=.
   	Therefore, when you do
   		XmFontListFree(VAR(old));
   		VAR(new) = XmFontListFree(VAR(new));
   	you really kill a pointer in the first line that you'll copy
   	in the next line.
   
   	Replace == by != and things work again.
MenuShell.c 1.64
   date: 1998/02/27 13:28:58;  author: rwscott;  state: Exp;  lines: +4 -26
   CascadeBG.c:ArmAndActivate() - currently I use an XmARM_EVENT to show the
   	button as armed. This however sets DragMode to True, so now reset
   	drag mode after the arm.  This will not be a problem when the
   	LabelMenuProcs get written for CascadeBG.
   
   MenuUtil.c:_XmMenuNextItem() - when searching for a valid control just use
   	XmIsTraversable(), it takes care of all of the other cases.
   
   MenuUtil.c:_XmMenuPrevItem() - see above
   
   MenuUtil.c:_XmMenuDisarmItem() - an XmLEAVE_EVENT to a gadget will only draw
   	the gadget un-armed if drag mode is on, therefore force the drag mode
   	to the value needed.  Again, this will not be necessary when the
   	LabelMenuProcs have been written for the Gadget buttons.
   
   RowColumn.c: Disarm the active child during a MENU_SHELL_POPDOWN
MenuShell.c 1.63
   date: 1998/02/22 21:42:23;  author: rwscott;  state: Exp;  lines: +3 -4
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
MenuShell.c 1.62
   date: 1998/02/22 04:42:18;  author: rwscott;  state: Exp;  lines: +12 -12
   Mainly comments as to what is going to be changing wrt the menu system.
   Basicly the way the label menu procs are used right now is wrong.  A label
   does not know if a particular button press is the correct button, this is a
   job for RowColumn, the official menu widget. The same is true for un-posting
   menus.  The label menu procs should be used by Label subclasses that can be
   in a menu system.  Through these procs the RowColumn can arm/disarm the
   controls without having to know the details of the control.
   
   So, what does all this mean.  The current contents of the Label[G] menu procs
   will be moved to RowColumn menu procs.  Label[G] menu procs will be written
   for each of the controls that can be in a menu. After that, nothing should
   care, or even know, about private/public menu shells.  All of this should
   be the responsibility of the routines in MenuShell.
   
   If anyone disagrees, now is the time to speak!
MenuShell.c 1.61
   date: 1998/02/22 01:00:44;  author: rwscott;  state: Exp;  lines: +31 -23
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
MenuShell.c 1.60
   date: 1998/02/20 05:45:24;  author: rwscott;  state: Exp;  lines: +3 -3
   Label.c - get rid of the FocusIn action this is actually in RowColumn
   	  Label still has a few more that need to move to RowColumn
   
   Manager.c:_XmAcceleratorHandler() - When an action proc is called directly
   	you must pass a pointer to the num_params, not NULL
   
   RowColumn - define the FocusIn action proc that was in Label
   
   AnythingElse - Debug stuff
MenuShell.c 1.59
   date: 1998/02/15 16:15:37;  author: rwscott;  state: Exp;  lines: +14 -5
   MenuShellPopdownDone - If the menu_shell is not PoppedUp nothing else
   	should need to be done, so just bail.  This happens in the case
   	of accelerators, the ArmAndActivate gets called and if the button
   	is in a menu the menu gets unposted.  When a menu gets unposted
   	a bunch of stuff gets disarmed which, in the case of accelerators
   	disables them.
   
   This was causing mgdiff to recognize only the first accelerator press after
   receiving focus.
MenuShell.c 1.58
   date: 1998/02/04 20:41:05;  author: u27113;  state: Exp;  lines: +13 -5
   FAQ : add question about LessTif 0.82 which thinks it's 0.81.
   Display.c : XdbDebug change, also NULL a pointer after freeing it.
   MenuShell.c : When using an accelerator, we XtUnmanageChild'd something
   	without a reason for it. This caused all kinds of strange things
   	to get called for no reason. Fixed.
   Draw.c : Found yet another reason for a loop overrun which caused a crash.
   	In XmeDrawArrow; happened in xmgr.
MenuShell.c 1.57
   date: 1998/01/06 20:38:52;  author: miers;  state: Exp;  lines: +3 -3
   Fix the one by one accelerator bug in mgdiff.  This was due to _XmMenuFocus()
   not quite doing the right thing for FOCUS_RESTORE.  Bug not fixed, just
   masked for now.
MenuShell.c 1.56
   date: 1997/12/21 14:16:53;  author: rwscott;  state: Exp;  lines: +76 -7
   This is all with respect to tearoffs.
   
   
   CascadeB.c
   
   	MenuBarEnter - Popdown the old menu only if a menushell (not torn off)
   
   	CascadePopupHandler - make sure the menu is back in its menu shell if
   		it was torn off
   
   	DelayedArm - Do not put a torn off menu back to its menushell here.
   		If the delay never times out then the menu is left in the
   		menu shell and never poped up.
   
   	CheckDisarm - If we have to popdown the menus use popdownEveryone.
   
   MenuShell.c
   
   	change_managed - If there are no managed children we pop down but, we
   	must popdown private shells different from public ones. Same goes for
   	popping up.
   
   	MenuShellPopdownOne - do not restore tear off to its toplevel shell
   	here, it just confuses popdowneveryone.
   
   	MenuShellPopdownEveryone - restore tear offs to their toplevel shells
   	here, after all the menus have been sorted out.
   
   	MenuShellPopupSharedMenuPane - Since we do not use XtPopup for menus
   	anymore we must take care of setting and un-setting of Shell_PoppedUp.
   	Not setting this was messing up <BtnDown> in push button and
   	probably other places (anywhere there was an if (Shell_PoppedUp)).
   
   PushB.c
   
   	Add some debug statements.
   
   RowColumn.c
   
   	DoBtnEventCleanupReplay - Do not call PopdownDone for a torn off menu
   
   	_XmGetActiveTopLevelMenu - Return something usefull for an active
   	tear off.
   
   TearOff.c
   
   	_XmTearOffBtnDownEventHandler - Arm the menu. Something a little
   	strange happens here, see the comments in the source.
   
   	_XmTearOffBtnUpEventHandler - DisArm the menu.
   
   	_XmTearOffInitiate - Get rid of the keyboard and pointer grabs from
   	the previous menu and turn off drag mode.
   
   	_XmAddTearOffEventHandlers - big time guess here! Add a button up
   	handler to the tear off and all of its widget children so we can
   	disarm the menu. Add a button down handler to all of the widget
   	children so we can arm the menu.
   
   	_XmRestoreTearOffToToplevelShell - Do not ungrab things here. The
   	grabs are now taken care of in the event handlers.
   	Do not reposition the shell if an event is not given.  This is due
   	the the MenuShell:change_managed call to put the menu back to the
   	toplevel shell.
   	Make sure the event handlers are in place.
   
   	_XmRestoreTearOffToMenuShell - Time for a little magic here! Ever
   	wonder how Motif keeps a copy of the tear off in the toplevel shell
   	and displays it in the menu at the same time?  Well you just take a
   	copy of the pixels in the toplevel shell before you re-parent the
   	menu and put those pixels into the shell.  Since the menu will have
   	grabs there is no way to interact with it so fake it!
   	I should be able to just set the background pixmap of the shell and
   	have X take care of the copy, stay tuned.
   	Do not unmanage the menu if it is in a private shell, they are always
   	managed.
MenuShell.c 1.55
   date: 1997/12/19 01:31:00;  author: rwscott;  state: Exp;  lines: +27 -6
   CascadeB.c:_XmCascadingPopup - before posting a menu make sure that it is in
   	it menushell.
   
   CascadeB.c:CheckDisarm - If we need to popdown a menu, use MenuShellPopdownOne
   	so that the menu will get restored to its toplevel shell if torn.
   
   MenuShell.c:MenuShellPopdownDone - If the menu is a popup do not unmanage it
   	if it is an active tearoff.
   
   MenuShell.c:MenuShellPopdownOne - If the menu is an active tearoff unpost any
   	menus posted from it and put it back into its toplevel shell.
   
   TearOff.c:_XmDismissTearOff - set the TearOffActive bit to 0
   TearOff.c:_XmTearOffInitiate - set the TearOffActive bit to 1
MenuShell.c 1.54
   date: 1997/12/16 03:18:03;  author: rwscott;  state: Exp;  lines: +5 -2
   CascadeB.c:StartDrag - If we are thinking of posting a menu make sure the
   	menu is put back into its menu shell if it was torn off.
   
   CascadeB.c:DelayedArm - ditto
   
   CascadeB.c:CheckDisarm - If we are thinking of un-posting a menu because
   	we are leaving the cascade button that posted it do not do it if
   	the menu is torn off.
   
   MenuShell.c:MenuShellPopdownEveryone - Do not recurse if the the shell is not
   	a menu shell, ie torn off.
   
   RowColumn.c:MenuEnter - If we are thinking of un-posting a menu, do not do
   	it if the menu is torn off.
   
   TearOff.c:_XmRestoreTearOffToMenuShell - XSync before we grab the server.
   	Do not XSync while the server is grabbed.  This was a fun one. It
   	seems that if you have the server grabbed in conjuction with
   	DEBUGSOURCES=all something gets bogged down and you get no response
   	if stderr is an xterm.  Re-direct to a file and all was ok.
   	Anyway, with the syncs and grabs altered a bit it seems okay.
MenuShell.c 1.53
   date: 1997/12/14 14:45:51;  author: rwscott;  state: Exp;  lines: +9 -2
   Label.c:label_menu_procs - case XmMENU_SHELL_POPDOWN -  If we have a menubar
   	with button1 and button2 and a tearoff is posted for button1 and we
   	click in button2 this routine gets called to popdown the menu for
   	button1.  Therefore if the menu to popdown is not in a menushell
   	leave it alone.
   
   MenuShell.c:MenuShellPopdownDone - If the top level widget is not a menushell
   	it must be a tearoff. In this case popdown everyone under the toplevel.
   
   TearOff.c:_XmTearOffInitiate - Preserve the value of RC_PopupPosted around the
   	call to MenuShellPopdownDone. Same as preserving the value of
   	RC_CascadeBtn.
   
   ToggleB.c:ButtonDown - Like most other places in this file when we set the
   	value for TB_IndicatorSet also set the value of TB_VisualSet.
   
   
   All of this was with tearoff/test2


MenuUtil.c Current rev 1.26 Last Release 1.10
MenuUtil.c 1.26
   date: 1998/03/09 14:48:47;  author: rwscott;  state: Exp;  lines: +3 -3
   _XmMenuArmItem() - special case when there is only 1 traversable item in
   	the menu.
MenuUtil.c 1.25
   date: 1998/03/08 18:43:07;  author: rwscott;  state: Exp;  lines: +3 -3
   Fixes from "Alexander Mai" <st002279@hrzpub.tu-darmstadt.de>
   
   I just turned -Wall back on for myself so things like this should not so
   easily slip by. It must have got turned off in the automake upgrade.
MenuUtil.c 1.24
   date: 1998/03/07 21:24:01;  author: rwscott;  state: Exp;  lines: +3 -4
   Some clean up as per the note from Alexander Mai
   
   
   How come I do not see those 'implicit declaration of function' warnings
   anymore?
MenuUtil.c 1.23
   date: 1998/03/02 17:14:08;  author: rwscott;  state: Exp;  lines: +6 -3
   _XmMenuDisarmItem - protection if called with NULL widget
MenuUtil.c 1.22
   date: 1998/03/02 04:30:31;  author: rwscott;  state: Exp;  lines: +31 -11
   MenuUtil.c - add unique event protection around the non-gadget traversal
   	handlers. This is needed in mixed gadget/widget menus.
   	ArmItem - set the focus _after_ a traversable item is found
   	Handle traverse right out of a cascade gadget
   
   RowColumn.c - debug stuff
   
   TearOff.c - Arm the first item on FocusIn, Disarm the active item on FocusOut.
MenuUtil.c 1.21
   date: 1998/03/01 23:03:17;  author: rwscott;  state: Exp;  lines: +8 -10
   CascadeB[G].c - general cleanup
   
   MenuUtil.c:_XmRC_GadgetTraverseLeft() - It seems that the event that causes
   	this can trigger this more than once.  Protect it with
   	_XmIsEventUnique/_XmRecordEvent.  This is where the strange behaviour
   	of mgdiff's menus during keyboard traversal was coming from.
MenuUtil.c 1.20
   date: 1998/03/01 19:22:12;  author: rwscott;  state: Exp;  lines: +19 -5
   ToggleB[G].c - general clean up
   
   MenuUtil.c:_XmMenuEscape() - watch out for gadgets when determining what type
   	of menu we are in.
   
   Just say NO, to Gadgets! (I think they are more of a pain than they are worth)
MenuUtil.c 1.19
   date: 1998/03/01 16:44:16;  author: rwscott;  state: Exp;  lines: +103 -10
   MenuUtil.c:_XmMenuEscape() - pretty much re-write this puppy.  Now that menus
   	are setting the appropriate RC instance variables this is a little
   	easier.  It also handles an escape in tear offs now (I had been
   	wondering how you got rid of a tear-off without the help of a
   	window manager).
   
   PushBG.c:initialize() - Only install the Label menu procs if we are in a menu.
   
   RowColumn.c:MenuProcEntry() - XmMENU_BUTTON_POPDOWN - do not set the memWidget
   	if it is a TearOffButton.  Also when we set the label on the cascade
   	button set it to the memWidget.
   
   RowColumn.c:MenuProcEntry() - XmMENU_SHELL_POPDOWN - do not disarm the active
   	child if the active child is making the call.
   
   RowColumn.c:_XmOptionCallback() - protection against being call with a NULL
   	widget.
   
   TearOff.c:_XmTearOffInitiate() - Bring down the menu shell with the RC procs
   
   TearOff.c: general clean up
   
   TearOffB.c: general clean up
MenuUtil.c 1.18
   date: 1998/02/28 18:41:59;  author: rwscott;  state: Exp;  lines: +7 -40
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
MenuUtil.c 1.17
   date: 1998/02/27 13:28:59;  author: rwscott;  state: Exp;  lines: +9 -7
   CascadeBG.c:ArmAndActivate() - currently I use an XmARM_EVENT to show the
   	button as armed. This however sets DragMode to True, so now reset
   	drag mode after the arm.  This will not be a problem when the
   	LabelMenuProcs get written for CascadeBG.
   
   MenuUtil.c:_XmMenuNextItem() - when searching for a valid control just use
   	XmIsTraversable(), it takes care of all of the other cases.
   
   MenuUtil.c:_XmMenuPrevItem() - see above
   
   MenuUtil.c:_XmMenuDisarmItem() - an XmLEAVE_EVENT to a gadget will only draw
   	the gadget un-armed if drag mode is on, therefore force the drag mode
   	to the value needed.  Again, this will not be necessary when the
   	LabelMenuProcs have been written for the Gadget buttons.
   
   RowColumn.c: Disarm the active child during a MENU_SHELL_POPDOWN
MenuUtil.c 1.16
   date: 1998/02/26 03:18:02;  author: miers;  state: Exp;  lines: +45 -38
   Rick, something that may help a bit.  Traversal in a menu also depends on
   traversalOn (or XmIsTraversable()), which was demonstrated by nedit's "fake"
   menu items.
   
   Label.c, LabelG.c:  Does anyone know why traversalOn was being set to FALSE
   for items in a menu?  Changed to highlightOnEnter set to false.
   
   MenuUtil.c: Check for not only a) not a Separator, and b) is XtSensitive(),
   but include c) XmIsTraversable().  This required a change to RowColumn.
   
   RowColumn.c: in widgetNavigable(), check for XtIsSensitive() and
   MGR_TraversalOn() and a) is WORK_AREA or OPTION_MENU, or b) is PULLDOWN or
   POPUP and !inDragMode, or c) is MENU_BAR and !inDragMode and PopupPosted.
   Any of those conditions are a navigable RC.
   
   Finally, you can probably lose (a) from MenuUtil, as a separator should never
   be navigable in a menu.  Also, a note to Chris: what is Netscape going to do
   about the dependencies on undocumented Motif data structures and functions
   in Communicator?  (Netscape is set to release the source to Communicator,
   if you didn't know: check out http://www.mozilla.org).  Somebody was asking
   on the list today about undocumented functions that Communicator uses
   (_XmDSIAddChild() et alia).  Will you have to have Motif source to contribute
   to Communicator?  Or will Motif DnD FINALLY be documented for the masses?
MenuUtil.c 1.15
   date: 1998/02/25 05:31:03;  author: rwscott;  state: Exp;  lines: +4 -2
   Clean toggleButton out of its intimate knowledge of the menu system.
   Each of the button types seem to have their own little tests when it comes
   to menus, all of which are getting concentrated in RowColumn for a more
   consistent treatment of the menus.
MenuUtil.c 1.14
   date: 1998/02/22 04:42:19;  author: rwscott;  state: Exp;  lines: +9 -6
   Mainly comments as to what is going to be changing wrt the menu system.
   Basicly the way the label menu procs are used right now is wrong.  A label
   does not know if a particular button press is the correct button, this is a
   job for RowColumn, the official menu widget. The same is true for un-posting
   menus.  The label menu procs should be used by Label subclasses that can be
   in a menu system.  Through these procs the RowColumn can arm/disarm the
   controls without having to know the details of the control.
   
   So, what does all this mean.  The current contents of the Label[G] menu procs
   will be moved to RowColumn menu procs.  Label[G] menu procs will be written
   for each of the controls that can be in a menu. After that, nothing should
   care, or even know, about private/public menu shells.  All of this should
   be the responsibility of the routines in MenuShell.
   
   If anyone disagrees, now is the time to speak!
MenuUtil.c 1.13
   date: 1998/02/21 01:50:10;  author: rwscott;  state: Exp;  lines: +233 -98
   With this keyboard traversal of menus should be possible. Feedback welcomed!
   
   CascadeB[G].c:ArmAndActivate() - If we post a submenu from a cascade button
   	in a menubar arm the first item in the menu. (Needs to be smarter
   	and arm the first active menu control)
   
   RowColumn.c - change the default radio behaviour back to False. This is wrong
   	according to misc/test16 but until we deal with it in other places
   	it messes up a bunch of toggle buttons in menus. See mgdiff->options
   	for an example.
   
   MenuUtil.c - Write all of the menu traversal handlers.....
   
   ToggleBG.c:[Enter|Leave]Window() - Do not insist on being in DragMode since
   	during keyboard traversal we are not.
MenuUtil.c 1.12
   date: 1998/02/17 19:43:49;  author: rwscott;  state: Exp;  lines: +21 -4
   allow keyboard traversal into a CascadeButton.
   
   All of this keyboard traversal of the menus is _very_ incomplete and buggy,
   bear with me......
MenuUtil.c 1.11
   date: 1998/02/17 13:31:50;  author: rwscott;  state: Exp;  lines: +103 -2
   First cut at keyboard traversal of menus.
   
   CascadeB[G].c:_XmCBMenuBarDoSelect - If we post a submenu then also arm the
   	first item.
   CascadeB[G].c:_XmCBMenuBarSelect - set MGR_ActiveChild for the parent
   
   MenuUtil.c - write a MenuTraversalHandler (A bit of a mess right now)
   
   PushB[G].c - set MGR_ActiveChild when Armed
   
   RowColumn.c - Install the traversal translations on MENU_BAR's.


MessageB.c Current rev 1.20 Last Release 1.19
MessageB.c 1.20
   date: 1998/02/22 01:00:45;  author: rwscott;  state: Exp;  lines: +7 -3
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


PanedW.c Current rev 1.32 Last Release 1.31
PanedW.c 1.32
   date: 1998/02/22 01:00:46;  author: rwscott;  state: Exp;  lines: +15 -7
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


Primitive.c Current rev 1.27 Last Release 1.24
Primitive.c 1.27
   date: 1997/11/22 18:37:12;  author: miers;  state: Exp;  lines: +2 -4
   MacrosI.h: Add macros for Core fields when we want them not as functions.
   
   Primitive.c: I accidentally removed one of the pixmap default functions.
   
   Visual.c: Gilles Seguin tells me that "unspecified_pixmap" is a valid string
   value for the various pixmaps -- it just means XmUNSPECIFIED_PIXMAP.
Primitive.c 1.26
   date: 1997/11/21 18:01:12;  author: miers;  state: Exp;  lines: +8 -8
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.
Primitive.c 1.25
   date: 1997/11/21 04:32:25;  author: miers;  state: Exp;  lines: +48 -2
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


Protocols.c Current rev 1.3 Last Release 1.2
Protocols.c 1.3
   date: 1998/02/22 01:00:47;  author: rwscott;  state: Exp;  lines: +8 -4
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


PushB.c Current rev 1.34 Last Release 1.22
PushB.c 1.34
   date: 1998/02/28 18:42:00;  author: rwscott;  state: Exp;  lines: +58 -2
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
PushB.c 1.33
   date: 1998/02/27 02:17:04;  author: rwscott;  state: Exp;  lines: +7 -120
   PushB[G].c:ArmAndActivate - call the ArmTimeout before the MenuButtonPopdown
   	since the popdown disarms the item, which means ArmTimeout will do
   	nothing.
   
   RowColumn:RC_MenuProcs MENU_BUTTON_POPDOWN - It turns out that the segfault
   	with accelerators was not because the menu was not popped up it was
   	because I was doing an MGR_ActiveChild on something that was not
   	an MGR !!
   
   
   Mitch, if you are still out there, CascadeBG's always seem to be ! Navigable,
   therefore failing the XmIsNavigable test in MenuUtil.  The same goes for
   PushBG's I think.  You can see this with mgdiff.  Take out the IsTraversable
   test in MenuUtil and you can use the arrow keys, with the test in you cannot.
PushB.c 1.32
   date: 1998/02/24 23:21:37;  author: rwscott;  state: Exp;  lines: +2 -4
   Bring PBG inline with PB.
PushB.c 1.31
   date: 1998/02/24 03:03:15;  author: rwscott;  state: Exp;  lines: +52 -56
   PushB.c - move the intimate knowledge of the menu system into RowColumn.
   	PushB needs to know when to bring a menu down but it should not
   	know the details of how to do so.
   
   RowColumn.c - Since all of the buttons are now bringing menus down through
   	the RC_MenuProcs the awfull option menu hack of adding a callback
   	to all of the buttons in the menu pane is no longer necessary.  The
   	function of the callback is now rolled into the code that brings
   	the menu down in response to a BtnUp event.
PushB.c 1.30
   date: 1998/02/23 01:33:02;  author: rwscott;  state: Exp;  lines: +32 -29
   ArmTimeout - This was not deallocating the memory allocated in ArmAndActivate
   	in all cases.
PushB.c 1.29
   date: 1998/02/22 21:42:24;  author: rwscott;  state: Exp;  lines: +22 -2
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
PushB.c 1.28
   date: 1998/02/22 14:42:02;  author: rwscott;  state: Exp;  lines: +10 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
PushB.c 1.27
   date: 1998/02/17 13:31:50;  author: rwscott;  state: Exp;  lines: +3 -2
   First cut at keyboard traversal of menus.
   
   CascadeB[G].c:_XmCBMenuBarDoSelect - If we post a submenu then also arm the
   	first item.
   CascadeB[G].c:_XmCBMenuBarSelect - set MGR_ActiveChild for the parent
   
   MenuUtil.c - write a MenuTraversalHandler (A bit of a mess right now)
   
   PushB[G].c - set MGR_ActiveChild when Armed
   
   RowColumn.c - Install the traversal translations on MENU_BAR's.
PushB.c 1.26
   date: 1997/12/26 21:39:25;  author: u27113;  state: Exp;  lines: +3 -3
   Add a trait.
PushB.c 1.25
   date: 1997/12/26 16:06:37;  author: u27113;  state: Exp;  lines: +39 -2
   INSTALL: some newer comments.
   
   PushB.c, PushBG.c : add trait.
   	It's been bothering me for a while that XmText lives in both
   	directories with only simple differences, this is a nightmare.
   
   	I'd like to see if we can keep SIMPLE 2.0 stuff in the 1.2 tree.
   	Barring a veto from you guys off course.
   
   	Currently my feeling is this : if we can get away with just
   	adding traits stuff by #ifdefs, do it in the 1.2 tree.
   
   Gadget.c : small fix to SetValues.
   
   Notebook.c : add some code. Not functional yet.
   Trait.c : small fix, don't really understand the problem.
   
   ActivatableT.h is a new trait header file.
PushB.c 1.24
   date: 1997/12/21 14:16:56;  author: rwscott;  state: Exp;  lines: +8 -2
   This is all with respect to tearoffs.
   
   
   CascadeB.c
   
   	MenuBarEnter - Popdown the old menu only if a menushell (not torn off)
   
   	CascadePopupHandler - make sure the menu is back in its menu shell if
   		it was torn off
   
   	DelayedArm - Do not put a torn off menu back to its menushell here.
   		If the delay never times out then the menu is left in the
   		menu shell and never poped up.
   
   	CheckDisarm - If we have to popdown the menus use popdownEveryone.
   
   MenuShell.c
   
   	change_managed - If there are no managed children we pop down but, we
   	must popdown private shells different from public ones. Same goes for
   	popping up.
   
   	MenuShellPopdownOne - do not restore tear off to its toplevel shell
   	here, it just confuses popdowneveryone.
   
   	MenuShellPopdownEveryone - restore tear offs to their toplevel shells
   	here, after all the menus have been sorted out.
   
   	MenuShellPopupSharedMenuPane - Since we do not use XtPopup for menus
   	anymore we must take care of setting and un-setting of Shell_PoppedUp.
   	Not setting this was messing up <BtnDown> in push button and
   	probably other places (anywhere there was an if (Shell_PoppedUp)).
   
   PushB.c
   
   	Add some debug statements.
   
   RowColumn.c
   
   	DoBtnEventCleanupReplay - Do not call PopdownDone for a torn off menu
   
   	_XmGetActiveTopLevelMenu - Return something usefull for an active
   	tear off.
   
   TearOff.c
   
   	_XmTearOffBtnDownEventHandler - Arm the menu. Something a little
   	strange happens here, see the comments in the source.
   
   	_XmTearOffBtnUpEventHandler - DisArm the menu.
   
   	_XmTearOffInitiate - Get rid of the keyboard and pointer grabs from
   	the previous menu and turn off drag mode.
   
   	_XmAddTearOffEventHandlers - big time guess here! Add a button up
   	handler to the tear off and all of its widget children so we can
   	disarm the menu. Add a button down handler to all of the widget
   	children so we can arm the menu.
   
   	_XmRestoreTearOffToToplevelShell - Do not ungrab things here. The
   	grabs are now taken care of in the event handlers.
   	Do not reposition the shell if an event is not given.  This is due
   	the the MenuShell:change_managed call to put the menu back to the
   	toplevel shell.
   	Make sure the event handlers are in place.
   
   	_XmRestoreTearOffToMenuShell - Time for a little magic here! Ever
   	wonder how Motif keeps a copy of the tear off in the toplevel shell
   	and displays it in the menu at the same time?  Well you just take a
   	copy of the pixels in the toplevel shell before you re-parent the
   	menu and put those pixels into the shell.  Since the menu will have
   	grabs there is no way to interact with it so fake it!
   	I should be able to just set the background pixmap of the shell and
   	have X take care of the copy, stay tuned.
   	Do not unmanage the menu if it is in a private shell, they are always
   	managed.
PushB.c 1.23
   date: 1997/11/21 04:32:27;  author: miers;  state: Exp;  lines: +36 -4
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


PushBG.c Current rev 1.33 Last Release 1.19
PushBG.c 1.33
   date: 1998/03/09 04:26:47;  author: rwscott;  state: Exp;  lines: +34 -4
   Changed the set_values debug and added a comment in ArmAndActivate about
   a problem that showed up in xdir.  In summary if the time out is used
   in ArmAndActivate instead of calling ArmTimeout directly xdir will segfault
   under certain conditions.  For more details take a look at the comments in
   ArmAndActivate.
PushBG.c 1.32
   date: 1998/03/07 21:24:02;  author: rwscott;  state: Exp;  lines: +6 -3
   Some clean up as per the note from Alexander Mai
   
   
   How come I do not see those 'implicit declaration of function' warnings
   anymore?
PushBG.c 1.31
   date: 1998/03/01 16:44:17;  author: rwscott;  state: Exp;  lines: +5 -3
   MenuUtil.c:_XmMenuEscape() - pretty much re-write this puppy.  Now that menus
   	are setting the appropriate RC instance variables this is a little
   	easier.  It also handles an escape in tear offs now (I had been
   	wondering how you got rid of a tear-off without the help of a
   	window manager).
   
   PushBG.c:initialize() - Only install the Label menu procs if we are in a menu.
   
   RowColumn.c:MenuProcEntry() - XmMENU_BUTTON_POPDOWN - do not set the memWidget
   	if it is a TearOffButton.  Also when we set the label on the cascade
   	button set it to the memWidget.
   
   RowColumn.c:MenuProcEntry() - XmMENU_SHELL_POPDOWN - do not disarm the active
   	child if the active child is making the call.
   
   RowColumn.c:_XmOptionCallback() - protection against being call with a NULL
   	widget.
   
   TearOff.c:_XmTearOffInitiate() - Bring down the menu shell with the RC procs
   
   TearOff.c: general clean up
   
   TearOffB.c: general clean up
PushBG.c 1.30
   date: 1998/02/28 18:42:01;  author: rwscott;  state: Exp;  lines: +61 -2
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
PushBG.c 1.29
   date: 1998/02/27 02:17:06;  author: rwscott;  state: Exp;  lines: +7 -66
   PushB[G].c:ArmAndActivate - call the ArmTimeout before the MenuButtonPopdown
   	since the popdown disarms the item, which means ArmTimeout will do
   	nothing.
   
   RowColumn:RC_MenuProcs MENU_BUTTON_POPDOWN - It turns out that the segfault
   	with accelerators was not because the menu was not popped up it was
   	because I was doing an MGR_ActiveChild on something that was not
   	an MGR !!
   
   
   Mitch, if you are still out there, CascadeBG's always seem to be ! Navigable,
   therefore failing the XmIsNavigable test in MenuUtil.  The same goes for
   PushBG's I think.  You can see this with mgdiff.  Take out the IsTraversable
   test in MenuUtil and you can use the arrow keys, with the test in you cannot.
PushBG.c 1.28
   date: 1998/02/24 23:21:38;  author: rwscott;  state: Exp;  lines: +66 -77
   Bring PBG inline with PB.
PushBG.c 1.27
   date: 1998/02/22 21:42:25;  author: rwscott;  state: Exp;  lines: +22 -2
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
PushBG.c 1.26
   date: 1998/02/22 14:42:03;  author: rwscott;  state: Exp;  lines: +10 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
PushBG.c 1.25
   date: 1998/02/22 01:00:48;  author: rwscott;  state: Exp;  lines: +16 -8
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
PushBG.c 1.24
   date: 1998/02/17 13:31:51;  author: rwscott;  state: Exp;  lines: +3 -2
   First cut at keyboard traversal of menus.
   
   CascadeB[G].c:_XmCBMenuBarDoSelect - If we post a submenu then also arm the
   	first item.
   CascadeB[G].c:_XmCBMenuBarSelect - set MGR_ActiveChild for the parent
   
   MenuUtil.c - write a MenuTraversalHandler (A bit of a mess right now)
   
   PushB[G].c - set MGR_ActiveChild when Armed
   
   RowColumn.c - Install the traversal translations on MENU_BAR's.
PushBG.c 1.23
   date: 1998/02/12 20:44:44;  author: rwscott;  state: Exp;  lines: +3 -2
   PushBG.c:set_values - added in a being_destroyed check because xdir was
   	segfaulting after typing in a password during a connect->remote.
   
   LabelG.c:set_values - refresh is needed if the sensitivity changes.
   	This was causing xdir's menu buttons to be shown in the wrong
   	state after a file transfer.
PushBG.c 1.22
   date: 1997/12/26 21:39:26;  author: u27113;  state: Exp;  lines: +3 -3
   Add a trait.
PushBG.c 1.21
   date: 1997/12/26 16:06:34;  author: u27113;  state: Exp;  lines: +40 -2
   INSTALL: some newer comments.
   
   PushB.c, PushBG.c : add trait.
   	It's been bothering me for a while that XmText lives in both
   	directories with only simple differences, this is a nightmare.
   
   	I'd like to see if we can keep SIMPLE 2.0 stuff in the 1.2 tree.
   	Barring a veto from you guys off course.
   
   	Currently my feeling is this : if we can get away with just
   	adding traits stuff by #ifdefs, do it in the 1.2 tree.
   
   Gadget.c : small fix to SetValues.
   
   Notebook.c : add some code. Not functional yet.
   Trait.c : small fix, don't really understand the problem.
   
   ActivatableT.h is a new trait header file.
PushBG.c 1.20
   date: 1997/11/21 04:32:28;  author: miers;  state: Exp;  lines: +32 -4
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


RCUtils.c Current rev 1.72 Last Release 1.68
RCUtils.c 1.72
   date: 1998/01/22 23:14:10;  author: u27113;  state: Exp;  lines: +7 -2
   Some updates to documents; HTML errors, a forgotten update to
   our version history, adding wxWindows.
   
   RCUtils : add XdbDebug trying to find Jon Christopher's problem.
   	Nothing yet.
RCUtils.c 1.71
   date: 1997/12/16 03:51:21;  author: rwscott;  state: Exp;  lines: +9 -2
   XmMenuPosition - Make sure the menu is back in its menu shell if it was
   	torn off.  This is not correct behaviour though.  Motif seems
   	happy to display the normal menu and the tear off at the same time.
   	How do they do that, clone the entire menu tree??
RCUtils.c 1.70
   date: 1997/12/14 22:03:50;  author: rwscott;  state: Exp;  lines: +4 -6
   _XmRCAdjustSize - Small tweak to the fix for filesb/test7. Just return
   	XtGeometryNo if we have no children. If we have some un-managed
   	children still run the layout. This is still necessary in the case
   	were we un-manage all of the kids.
RCUtils.c 1.69
   date: 1997/12/13 22:27:05;  author: rwscott;  state: Exp;  lines: +14 -2
   GeoUtils.c:_XmMenuBarFix - Add in a GET_PREFERRED_SIZE action to query the
   	preferred size of the menubar.
   
   RCUtils.c:_XmRCPreferredSize - We were simply returning if the RC had no
   	managed children.  This results in the RC remaining its current size.
   	However if we have an RC with a bunch of kids and then unmanage them
   	all, we want the RC to shrink. Therefore even if we have no managed
   	children go through the whole layout deal.
   
   RCUtils.c:_XmRCAdjustSize - ditto
   
   This is all in aid of filesb/test7.  The exact behaviour needs to be compared
   to Motif but hey, I do not have Motif!


Region.c Current rev 1.3 Last Release 1.2
Region.c 1.3
   date: 1998/02/11 21:15:12;  author: u27113;  state: Exp;  lines: +8 -4
   lib/Xm/Makefile.am, lib/Mrm/Makefile.am :
   	fix version numbers on Linux
   	Libtool has a rather strange way of calculating them on Linux,
   	it's more normal for FreeBSD so I never noticed.
   
   lib/Mrm/Region.c :
   	remove memory leak as indicated by Alan Curry <pacman@cqc.com>
   
   doc/www.lesstif.org/working.html :
   	Change status of Xquote. Its web site says it works.
   
   scripts/mmf :
   	More intelligent version.
   
   CURRENT_NOTES : change comment for mmf slightly
   
   include/Motif-1.2/Xm/Makefile.am, include/Motif-2.0/Xm/Makefile.am :
   	Make sure Xm.h (which is built by configure and may therefore
   	be in a build directory tree which is potentially different
   	from the source directory tree) gets installed right.


ResConvert.c Current rev 1.19 Last Release 1.15
ResConvert.c 1.19
   date: 1998/03/06 22:09:28;  author: u27113;  state: Exp;  lines: +17 -3
   Fixes to get TWLOG to work
   	(see mail from Joop Stakenborg <jsg@abapc.kfih.azr.nl>)
   
   ResConvert.c : fix a problem in converter.
   	Always the same: the problem with returning stuff whose size
   	is bigger than a pointer.
   
   Xm.h : twlog also uses XmTextSetTopPosition which is the same as
   	XmTextSetTopCharacter.
ResConvert.c 1.18
   date: 1998/03/04 20:45:55;  author: u27113;  state: Exp;  lines: +65 -2
   lib/Xm/ResConvert.c lib/Xm-2.0/ResConvert.c
   	Add String To Cardinal converter as submitted by Paul Flinders
   	<paul@dawa.demon.co.uk>.
   
   lib/*/Makefile.am
   	Don't use the 0.82 etc. numbers in libtool command.
ResConvert.c 1.17
   date: 1998/01/08 15:07:45;  author: miers;  state: Exp;  lines: +4 -4
   Xm.h: Bump version number to correct value.
   
   ResConvert.c: Change #ifndef to #ifdef
ResConvert.c 1.16
   date: 1997/12/28 21:34:52;  author: u27113;  state: Exp;  lines: +4 -4
   Remove leading and trailing " in font lists.
   Also modify the macro that includes nonstandard converters,
   and build it into the configuration.
   
   Configuration: also add the test Makefiles.


RowColumn.c Current rev 1.138 Last Release 1.103
RowColumn.c 1.138
   date: 1998/03/13 22:25:33;  author: rwscott;  state: Exp;  lines: +10 -4
   RC_Procs - MENU_SHELL_POPDOWN - Get rid of the warning that Alexander has
   	been commenting on for a while.  I do'nt think it is entirly
   	correct but, until I find out whether or not RC_PopupPosted stays
   	set when a menu gets torn off it will do.
   
   Also added a comment around where a shell gets popped up.  With respect to
   tear-offs we have to add a grab back in when the menu gets posted back to
   the menu-shell from the tear off. I am not real comfortable leaving this in,
   but I do not want to lose it, so it is there commented out.
RowColumn.c 1.137
   date: 1998/03/10 15:11:20;  author: rwscott;  state: Exp;  lines: +3 -3
   MenuProcs XmMENU_SUBMENU - when assigning a submenu to a button watch out
   	for Gadgets.
RowColumn.c 1.136
   date: 1998/03/09 00:30:16;  author: rwscott;  state: Exp;  lines: +8 -2
   _XmPopupButtonPressHandler() - We enter this routine by way of XtGrabButton
   	which sets up a pointer and keyboard grab.  Therefore no matter
   	how we leave this routine make sure that the grabs are released.
   	This showed up in xephem View->moon and View->earth(spherical) when
   	button 3 was pressed outside of the moon/earth.
RowColumn.c 1.135
   date: 1998/03/08 23:44:07;  author: rwscott;  state: Exp;  lines: +12 -3
   Put the tm_table back to XtInheriteTranslations.  With a NULL here we loose
   toggle button gadgets in a work area, togglegb/test1.  I suspect that
   the init pre-hook should be installing the appropriate translations for
   a work area. It handles all the other types of row columns.
RowColumn.c 1.134
   date: 1998/03/08 21:59:29;  author: rwscott;  state: Exp;  lines: +5 -6
   A couple of suggestions from the '-Wall'
RowColumn.c 1.133
   date: 1998/03/05 14:44:48;  author: rwscott;  state: Exp;  lines: +3 -3
   A debug statement was trying to print the name of the RC_LastSelectTopLevel
   of a popup menu. Of course RC_LastSelectTopLevel for a popup is null.
RowColumn.c 1.132
   date: 1998/03/02 04:30:32;  author: rwscott;  state: Exp;  lines: +5 -4
   MenuUtil.c - add unique event protection around the non-gadget traversal
   	handlers. This is needed in mixed gadget/widget menus.
   	ArmItem - set the focus _after_ a traversable item is found
   	Handle traverse right out of a cascade gadget
   
   RowColumn.c - debug stuff
   
   TearOff.c - Arm the first item on FocusIn, Disarm the active item on FocusOut.
RowColumn.c 1.131
   date: 1998/03/02 01:26:35;  author: rwscott;  state: Exp;  lines: +10 -2
   TearOff.c:BtnUpEventHandler - Do not disarm the menu if the menu has something
   	posted. This allows catching button events that are external to the
   	menu system and unposting whatever is posted.
   
   TearOff.c:RestoreToMenuShell - make sure that the menu is disarmed before it
   	is returned to the menu shell otherwise the events go to the
   	transient shell, which is not in use.
   
   RowColumn.c:MenuProcs - MENU_CASCADING - make sure to set the active child
   	of the menu we are cascading from and highlight the button.
   
   RowColumn.c:DoBtnEventCleanupReplay() - If the menu is not in a menu shell
   	check for a tearoff.
   
   I don't think that _XmGetActiveTopLevelMenu is returning the correct thing.
   If a pulldown is posted from a menu bar the top level menu should be the
   menu bar.  _XmGetActiveTopLevelMenu is returning the pulldown that the
   menu bar has posted.  However, you add in tearoffs and things get very
   confusing.  This needs a closer look.
RowColumn.c 1.130
   date: 1998/03/01 16:44:18;  author: rwscott;  state: Exp;  lines: +17 -11
   MenuUtil.c:_XmMenuEscape() - pretty much re-write this puppy.  Now that menus
   	are setting the appropriate RC instance variables this is a little
   	easier.  It also handles an escape in tear offs now (I had been
   	wondering how you got rid of a tear-off without the help of a
   	window manager).
   
   PushBG.c:initialize() - Only install the Label menu procs if we are in a menu.
   
   RowColumn.c:MenuProcEntry() - XmMENU_BUTTON_POPDOWN - do not set the memWidget
   	if it is a TearOffButton.  Also when we set the label on the cascade
   	button set it to the memWidget.
   
   RowColumn.c:MenuProcEntry() - XmMENU_SHELL_POPDOWN - do not disarm the active
   	child if the active child is making the call.
   
   RowColumn.c:_XmOptionCallback() - protection against being call with a NULL
   	widget.
   
   TearOff.c:_XmTearOffInitiate() - Bring down the menu shell with the RC procs
   
   TearOff.c: general clean up
   
   TearOffB.c: general clean up
RowColumn.c 1.129
   date: 1998/02/28 18:42:02;  author: rwscott;  state: Exp;  lines: +194 -2
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
RowColumn.c 1.128
   date: 1998/02/27 22:23:25;  author: rwscott;  state: Exp;  lines: +25 -4
   Get rid of the FixOptionMenu calls.  This is replaced by the RC_MenuProc
   XmMENU_SUBMENU which does essentially the same thing except that it is
   now under the control of RC.
RowColumn.c 1.127
   date: 1998/02/27 13:29:00;  author: rwscott;  state: Exp;  lines: +16 -4
   CascadeBG.c:ArmAndActivate() - currently I use an XmARM_EVENT to show the
   	button as armed. This however sets DragMode to True, so now reset
   	drag mode after the arm.  This will not be a problem when the
   	LabelMenuProcs get written for CascadeBG.
   
   MenuUtil.c:_XmMenuNextItem() - when searching for a valid control just use
   	XmIsTraversable(), it takes care of all of the other cases.
   
   MenuUtil.c:_XmMenuPrevItem() - see above
   
   MenuUtil.c:_XmMenuDisarmItem() - an XmLEAVE_EVENT to a gadget will only draw
   	the gadget un-armed if drag mode is on, therefore force the drag mode
   	to the value needed.  Again, this will not be necessary when the
   	LabelMenuProcs have been written for the Gadget buttons.
   
   RowColumn.c: Disarm the active child during a MENU_SHELL_POPDOWN
RowColumn.c 1.126
   date: 1998/02/27 05:04:23;  author: rwscott;  state: Exp;  lines: +9 -3
   Move most of CascadeButton's knowledge of menus to the RC_MenuProcs. Still
   to go is the knowledge of how to popup a menu.  All that should be done
   from CascadeButton is call the RC_MenuProc XmMENU_CASCADING and RC will take
   care of placing it correctly.  Again I think the code that handles this is
   correct, just misplaced.
RowColumn.c 1.125
   date: 1998/02/27 02:17:07;  author: rwscott;  state: Exp;  lines: +6 -6
   PushB[G].c:ArmAndActivate - call the ArmTimeout before the MenuButtonPopdown
   	since the popdown disarms the item, which means ArmTimeout will do
   	nothing.
   
   RowColumn:RC_MenuProcs MENU_BUTTON_POPDOWN - It turns out that the segfault
   	with accelerators was not because the menu was not popped up it was
   	because I was doing an MGR_ActiveChild on something that was not
   	an MGR !!
   
   
   Mitch, if you are still out there, CascadeBG's always seem to be ! Navigable,
   therefore failing the XmIsNavigable test in MenuUtil.  The same goes for
   PushBG's I think.  You can see this with mgdiff.  Take out the IsTraversable
   test in MenuUtil and you can use the arrow keys, with the test in you cannot.
RowColumn.c 1.124
   date: 1998/02/26 20:14:30;  author: rwscott;  state: Exp;  lines: +6 -6
   In MENU_BUTTON_POPDOWN do not try to disarm the menuitem if the menu is not
   popped up.  This was segfaulting when the item was armed via an accelerator
RowColumn.c 1.123
   date: 1998/02/26 03:18:03;  author: miers;  state: Exp;  lines: +6 -3
   Rick, something that may help a bit.  Traversal in a menu also depends on
   traversalOn (or XmIsTraversable()), which was demonstrated by nedit's "fake"
   menu items.
   
   Label.c, LabelG.c:  Does anyone know why traversalOn was being set to FALSE
   for items in a menu?  Changed to highlightOnEnter set to false.
   
   MenuUtil.c: Check for not only a) not a Separator, and b) is XtSensitive(),
   but include c) XmIsTraversable().  This required a change to RowColumn.
   
   RowColumn.c: in widgetNavigable(), check for XtIsSensitive() and
   MGR_TraversalOn() and a) is WORK_AREA or OPTION_MENU, or b) is PULLDOWN or
   POPUP and !inDragMode, or c) is MENU_BAR and !inDragMode and PopupPosted.
   Any of those conditions are a navigable RC.
   
   Finally, you can probably lose (a) from MenuUtil, as a separator should never
   be navigable in a menu.  Also, a note to Chris: what is Netscape going to do
   about the dependencies on undocumented Motif data structures and functions
   in Communicator?  (Netscape is set to release the source to Communicator,
   if you didn't know: check out http://www.mozilla.org).  Somebody was asking
   on the list today about undocumented functions that Communicator uses
   (_XmDSIAddChild() et alia).  Will you have to have Motif source to contribute
   to Communicator?  Or will Motif DnD FINALLY be documented for the masses?
RowColumn.c 1.122
   date: 1998/02/25 05:46:48;  author: rwscott;  state: Exp;  lines: +2 -6
   Opps, I left a couple of printf's in
RowColumn.c 1.121
   date: 1998/02/25 05:31:05;  author: rwscott;  state: Exp;  lines: +14 -2
   Clean toggleButton out of its intimate knowledge of the menu system.
   Each of the button types seem to have their own little tests when it comes
   to menus, all of which are getting concentrated in RowColumn for a more
   consistent treatment of the menus.
RowColumn.c 1.120
   date: 1998/02/24 03:03:18;  author: rwscott;  state: Exp;  lines: +37 -9
   PushB.c - move the intimate knowledge of the menu system into RowColumn.
   	PushB needs to know when to bring a menu down but it should not
   	know the details of how to do so.
   
   RowColumn.c - Since all of the buttons are now bringing menus down through
   	the RC_MenuProcs the awfull option menu hack of adding a callback
   	to all of the buttons in the menu pane is no longer necessary.  The
   	function of the callback is now rolled into the code that brings
   	the menu down in response to a BtnUp event.
RowColumn.c 1.119
   date: 1998/02/22 21:42:26;  author: rwscott;  state: Exp;  lines: +78 -4
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
RowColumn.c 1.118
   date: 1998/02/22 14:42:04;  author: rwscott;  state: Exp;  lines: +67 -4
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
RowColumn.c 1.117
   date: 1998/02/21 01:50:11;  author: rwscott;  state: Exp;  lines: +5 -3
   With this keyboard traversal of menus should be possible. Feedback welcomed!
   
   CascadeB[G].c:ArmAndActivate() - If we post a submenu from a cascade button
   	in a menubar arm the first item in the menu. (Needs to be smarter
   	and arm the first active menu control)
   
   RowColumn.c - change the default radio behaviour back to False. This is wrong
   	according to misc/test16 but until we deal with it in other places
   	it messes up a bunch of toggle buttons in menus. See mgdiff->options
   	for an example.
   
   MenuUtil.c - Write all of the menu traversal handlers.....
   
   ToggleBG.c:[Enter|Leave]Window() - Do not insist on being in DragMode since
   	during keyboard traversal we are not.
RowColumn.c 1.116
   date: 1998/02/20 15:11:03;  author: rwscott;  state: Exp;  lines: +88 -32
   Label.c - Move some more of the actions over to RowColumn (see misc/test16)
   
   RowColumn - define the actions that used to be in Label
   	bring the class structure and default resources more in-line with
   	Motif (see misc/test16)
RowColumn.c 1.115
   date: 1998/02/20 05:45:25;  author: rwscott;  state: Exp;  lines: +14 -2
   Label.c - get rid of the FocusIn action this is actually in RowColumn
   	  Label still has a few more that need to move to RowColumn
   
   Manager.c:_XmAcceleratorHandler() - When an action proc is called directly
   	you must pass a pointer to the num_params, not NULL
   
   RowColumn - define the FocusIn action proc that was in Label
   
   AnythingElse - Debug stuff
RowColumn.c 1.114
   date: 1998/02/18 22:15:58;  author: rwscott;  state: Exp;  lines: +7 -2
   Create the tear-off control in initialize if tear offs are enabled at this
   point.
RowColumn.c 1.113
   date: 1998/02/17 13:31:53;  author: rwscott;  state: Exp;  lines: +4 -3
   First cut at keyboard traversal of menus.
   
   CascadeB[G].c:_XmCBMenuBarDoSelect - If we post a submenu then also arm the
   	first item.
   CascadeB[G].c:_XmCBMenuBarSelect - set MGR_ActiveChild for the parent
   
   MenuUtil.c - write a MenuTraversalHandler (A bit of a mess right now)
   
   PushB[G].c - set MGR_ActiveChild when Armed
   
   RowColumn.c - Install the traversal translations on MENU_BAR's.
RowColumn.c 1.112
   date: 1998/01/27 19:59:47;  author: u27113;  state: Exp;  lines: +11 -4
   INSTALL : updated
   configure.in, 2.0/Xm/Xm.h.in : same story as 1.2 version.
   
   1.2/Xm/Xm.h.in : replace "alpha" which was there since 0.80 alpha
   	by PICO_VERSION
   
   RowColumn.c : add XClearArea to expose() to redraw yourself correctly
   	when resizing to become bigger
   
   Makefile.am : work with a 2.0 tree as well
RowColumn.c 1.111
   date: 1997/12/21 14:16:57;  author: rwscott;  state: Exp;  lines: +20 -2
   This is all with respect to tearoffs.
   
   
   CascadeB.c
   
   	MenuBarEnter - Popdown the old menu only if a menushell (not torn off)
   
   	CascadePopupHandler - make sure the menu is back in its menu shell if
   		it was torn off
   
   	DelayedArm - Do not put a torn off menu back to its menushell here.
   		If the delay never times out then the menu is left in the
   		menu shell and never poped up.
   
   	CheckDisarm - If we have to popdown the menus use popdownEveryone.
   
   MenuShell.c
   
   	change_managed - If there are no managed children we pop down but, we
   	must popdown private shells different from public ones. Same goes for
   	popping up.
   
   	MenuShellPopdownOne - do not restore tear off to its toplevel shell
   	here, it just confuses popdowneveryone.
   
   	MenuShellPopdownEveryone - restore tear offs to their toplevel shells
   	here, after all the menus have been sorted out.
   
   	MenuShellPopupSharedMenuPane - Since we do not use XtPopup for menus
   	anymore we must take care of setting and un-setting of Shell_PoppedUp.
   	Not setting this was messing up <BtnDown> in push button and
   	probably other places (anywhere there was an if (Shell_PoppedUp)).
   
   PushB.c
   
   	Add some debug statements.
   
   RowColumn.c
   
   	DoBtnEventCleanupReplay - Do not call PopdownDone for a torn off menu
   
   	_XmGetActiveTopLevelMenu - Return something usefull for an active
   	tear off.
   
   TearOff.c
   
   	_XmTearOffBtnDownEventHandler - Arm the menu. Something a little
   	strange happens here, see the comments in the source.
   
   	_XmTearOffBtnUpEventHandler - DisArm the menu.
   
   	_XmTearOffInitiate - Get rid of the keyboard and pointer grabs from
   	the previous menu and turn off drag mode.
   
   	_XmAddTearOffEventHandlers - big time guess here! Add a button up
   	handler to the tear off and all of its widget children so we can
   	disarm the menu. Add a button down handler to all of the widget
   	children so we can arm the menu.
   
   	_XmRestoreTearOffToToplevelShell - Do not ungrab things here. The
   	grabs are now taken care of in the event handlers.
   	Do not reposition the shell if an event is not given.  This is due
   	the the MenuShell:change_managed call to put the menu back to the
   	toplevel shell.
   	Make sure the event handlers are in place.
   
   	_XmRestoreTearOffToMenuShell - Time for a little magic here! Ever
   	wonder how Motif keeps a copy of the tear off in the toplevel shell
   	and displays it in the menu at the same time?  Well you just take a
   	copy of the pixels in the toplevel shell before you re-parent the
   	menu and put those pixels into the shell.  Since the menu will have
   	grabs there is no way to interact with it so fake it!
   	I should be able to just set the background pixmap of the shell and
   	have X take care of the copy, stay tuned.
   	Do not unmanage the menu if it is in a private shell, they are always
   	managed.
RowColumn.c 1.110
   date: 1997/12/16 03:18:04;  author: rwscott;  state: Exp;  lines: +8 -5
   CascadeB.c:StartDrag - If we are thinking of posting a menu make sure the
   	menu is put back into its menu shell if it was torn off.
   
   CascadeB.c:DelayedArm - ditto
   
   CascadeB.c:CheckDisarm - If we are thinking of un-posting a menu because
   	we are leaving the cascade button that posted it do not do it if
   	the menu is torn off.
   
   MenuShell.c:MenuShellPopdownEveryone - Do not recurse if the the shell is not
   	a menu shell, ie torn off.
   
   RowColumn.c:MenuEnter - If we are thinking of un-posting a menu, do not do
   	it if the menu is torn off.
   
   TearOff.c:_XmRestoreTearOffToMenuShell - XSync before we grab the server.
   	Do not XSync while the server is grabbed.  This was a fun one. It
   	seems that if you have the server grabbed in conjuction with
   	DEBUGSOURCES=all something gets bogged down and you get no response
   	if stderr is an xterm.  Re-direct to a file and all was ok.
   	Anyway, with the syncs and grabs altered a bit it seems okay.
RowColumn.c 1.109
   date: 1997/12/11 23:07:50;  author: u27113;  state: Exp;  lines: +4 -2
   FAQ : badly needed an update.
   lesstif.html :
   get.html : add mirror information
   CURRENT_NOTES : stuff about configuration
   configure.in : now static libraries don't get built by default
   
   SpinBox.c : add stuff for Uli's bug report.
   	Forgot to call a function in ConstraintInitialize
   
   lib/Xm-2.0/Makefile.am : works better this way; harder to maintain though.
   
   RowColumn.c : there was an unprotected printf here.
   	#ifdeffed it out.
RowColumn.c 1.108
   date: 1997/12/08 11:02:17;  author: rwscott;  state: Exp;  lines: +12 -2
   _XmRadioCallback - get the behaviour back for rowcolumn/test31
RowColumn.c 1.107
   date: 1997/12/05 23:08:08;  author: u27113;  state: Exp;  lines: +2 -12
   Add a few files to be able to configure the tests too.
   Automake, autoconf should be run nightly on test/* .
   I'll handle that next week.
   
   Futher: a bug fix for Steven Danz's problem with bulletinboard.
   Also added IPE to the list of working apps, fixed a URL too.
RowColumn.c 1.106
   date: 1997/12/05 01:11:36;  author: rwscott;  state: Exp;  lines: +14 -2
   _XmRadioCallback - get the correct behaviour for rowcolumn/test31
   
   Hey, I can't build the tests anymore.
RowColumn.c 1.105
   date: 1997/11/22 05:31:08;  author: miers;  state: Exp;  lines: +22 -68
   MacrosI.h: Add a macro for GrabKind in Shell.
   
   RowColumn.c: Alter the menuPost import operator to use _XmMapBtnEvent.
   
   TextOut.c: *One* of Andreas' patches.  I don't know enough about the
   other one.
   
   Todo: nedit (latest version) has a popup menu that they are using
   XtManageChild() *AND* XtPopup(x, XtGrabNonexclusive) on.  This, needless
   to say, doesn't work with our grab mechanics very well.  Motif somehow
   copes.  Sigh.
RowColumn.c 1.104
   date: 1997/11/21 18:01:14;  author: miers;  state: Exp;  lines: +5 -5
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.


Sash.c Current rev 1.10 Last Release 1.9
Sash.c 1.10
   date: 1998/02/22 01:00:49;  author: rwscott;  state: Exp;  lines: +10 -27
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


Scale.c Current rev 1.23 Last Release 1.22
Scale.c 1.23
   date: 1998/02/22 01:00:50;  author: rwscott;  state: Exp;  lines: +4 -4
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


Screen.c Current rev 1.10 Last Release 1.9
Screen.c 1.10
   date: 1998/02/22 01:00:51;  author: rwscott;  state: Exp;  lines: +7 -14
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


ScrollBar.c Current rev 1.21 Last Release 1.16
ScrollBar.c 1.21
   date: 1998/03/10 20:20:23;  author: helden;  state: Exp;  lines: +2 -7
   Fix by Dan <oramd@cs.man.ac.uk>. XmScrollBarSetValues now positions the slider
   correctly.
ScrollBar.c 1.20
   date: 1998/03/04 22:13:25;  author: rwscott;  state: Exp;  lines: +61 -3
   I have had this one kicking around for a while, time to get rid of it.
   
   If the backgroundPixmap is specified use it for the background instead of
   the troughColor.  This shows up in mgdiff.  The two scrollbars on the right
   have pretty colored lines drawn on the backgroundPixmap.
ScrollBar.c 1.19
   date: 1998/02/22 01:00:52;  author: rwscott;  state: Exp;  lines: +14 -7
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
ScrollBar.c 1.18
   date: 1997/12/29 22:03:46;  author: helden;  state: Exp;  lines: +48 -4
   Fix the reported orientation SetValues problem.
ScrollBar.c 1.17
   date: 1997/12/11 21:38:57;  author: helden;  state: Exp;  lines: +22 -2
   Playing with Mosaic and XmHTML on slow hardware revealed a timing problem
   with scrolling. When scrolling is really slow what happens is that the
   repeat timer goes off before the scrolling is completed; resulting in
   in a couple of other scrolls. Inserted XSync's to fix this.


ScrolledW.c Current rev 1.68 Last Release 1.67
ScrolledW.c 1.68
   date: 1998/02/22 01:00:53;  author: rwscott;  state: Exp;  lines: +14 -14
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


SelectionBox.c Current rev 1.24 Last Release 1.20
SelectionBox.c 1.24
   date: 1998/03/12 23:45:21;  author: rwscott;  state: Exp;  lines: +8 -2
   insert_child() - Before ParentProcessActivate we needed to add an activate
   	callback to all the TextField children to get the behaviour correct.
   	Now that TextField calls ParentProcessActivate in response to the
   	activate event this extra callback was causing the dialog okCallback
   	to get called twice.
   
   This may have been the problem with the nedit save as function, since
   FileSelectionBox is a subclass of SelectionBox (I did not check).
SelectionBox.c 1.23
   date: 1998/02/22 01:00:54;  author: rwscott;  state: Exp;  lines: +10 -19
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
SelectionBox.c 1.22
   date: 1998/02/07 03:16:30;  author: rwscott;  state: Exp;  lines: +6 -6
   Changed the names of the sub-widgets as per the report from
   fred pesch <pesch@club-internet.fr> (My small part to help eXode)
SelectionBox.c 1.21
   date: 1997/11/25 00:36:11;  author: rwscott;  state: Exp;  lines: +20 -3
   initialize: handle being initialized with an itemList.


SeparatoG.c Current rev 1.7 Last Release 1.5
SeparatoG.c 1.7
   date: 1998/02/22 01:00:55;  author: rwscott;  state: Exp;  lines: +21 -22
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
SeparatoG.c 1.6
   date: 1998/01/09 15:18:10;  author: miers;  state: Exp;  lines: +6 -3
   Danny's changes.
   
   CURRENT_NOTES: Add comments about what happened.
   ltconfig ltmain.sh: introduce libtool-1.0h instead of 1.0
   include/Motif-2.0/Xm/NavigatorT.h: new trait
   include/Motif-2.0/Xm/ScrollFrameT.h: update for trait
   include/Motif-2.0/Xm/PanedWP.h: new include file
   lib/Xm-2.0/PanedW.c: new widget supporting orientation
   lib/Xm-2.0/Notebook.c, SpinBox.c: NB works better, several SpinBox enhancements
   lib/Xm/Separator.c, SeparatoG.c: bug fix, ignored orientation in set_values -
                                    show in 2.0 PanedW
   clients/Motif-1.2/*/Makefile.am: include version_suffix (mlm: removed
                                    bogus mwmlex.h) to support building 2.0 clients
   test/Xm/panedw/test8.c: 2.0 panedw test


Separator.c Current rev 1.6 Last Release 1.4
Separator.c 1.6
   date: 1998/02/22 01:00:56;  author: rwscott;  state: Exp;  lines: +23 -14
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
Separator.c 1.5
   date: 1998/01/09 15:18:13;  author: miers;  state: Exp;  lines: +9 -4
   Danny's changes.
   
   CURRENT_NOTES: Add comments about what happened.
   ltconfig ltmain.sh: introduce libtool-1.0h instead of 1.0
   include/Motif-2.0/Xm/NavigatorT.h: new trait
   include/Motif-2.0/Xm/ScrollFrameT.h: update for trait
   include/Motif-2.0/Xm/PanedWP.h: new include file
   lib/Xm-2.0/PanedW.c: new widget supporting orientation
   lib/Xm-2.0/Notebook.c, SpinBox.c: NB works better, several SpinBox enhancements
   lib/Xm/Separator.c, SeparatoG.c: bug fix, ignored orientation in set_values -
                                    show in 2.0 PanedW
   clients/Motif-1.2/*/Makefile.am: include version_suffix (mlm: removed
                                    bogus mwmlex.h) to support building 2.0 clients
   test/Xm/panedw/test8.c: 2.0 panedw test


Shadow.c Current rev 1.10 Last Release 1.8
Shadow.c 1.10
   date: 1997/11/21 18:01:16;  author: miers;  state: Exp;  lines: +2 -8
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.
Shadow.c 1.9
   date: 1997/11/21 04:32:29;  author: miers;  state: Exp;  lines: +34 -2
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


ShellExt.c Current rev 1.3 Last Release 1.2
ShellExt.c 1.3
   date: 1998/02/22 01:00:57;  author: rwscott;  state: Exp;  lines: +7 -45
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


Simple.c Current rev 1.13 Last Release 1.10
Simple.c 1.13
   date: 1997/12/07 13:55:29;  author: rwscott;  state: Exp;  lines: +64 -58
   XmCreateSimplePopupMenu - use the default button type when the button_type
   	array is not given.
Simple.c 1.12
   date: 1997/12/05 17:30:41;  author: rwscott;  state: Exp;  lines: +43 -22
   XmCreateSimplePulldownMenu - If the button_type list is not given default
   	to XmPUSHBUTTON  (rowcolumn/test32)
Simple.c 1.11
   date: 1997/11/29 14:03:29;  author: rwscott;  state: Exp;  lines: +40 -14
   XmCreateSimpleOptionMenu - Stop this from segfaulting when the button
   	type table is not given. Default to XmCASCADEBUTTON in a MENU_BAR
   	and XmPUSHBUTTON in everything else.


TearOff.c Current rev 1.23 Last Release 1.10
TearOff.c 1.23
   date: 1998/03/08 21:59:30;  author: rwscott;  state: Exp;  lines: +3 -2
   A couple of suggestions from the '-Wall'
TearOff.c 1.22
   date: 1998/03/02 04:30:33;  author: rwscott;  state: Exp;  lines: +4 -4
   MenuUtil.c - add unique event protection around the non-gadget traversal
   	handlers. This is needed in mixed gadget/widget menus.
   	ArmItem - set the focus _after_ a traversable item is found
   	Handle traverse right out of a cascade gadget
   
   RowColumn.c - debug stuff
   
   TearOff.c - Arm the first item on FocusIn, Disarm the active item on FocusOut.
TearOff.c 1.21
   date: 1998/03/02 01:26:36;  author: rwscott;  state: Exp;  lines: +25 -2
   TearOff.c:BtnUpEventHandler - Do not disarm the menu if the menu has something
   	posted. This allows catching button events that are external to the
   	menu system and unposting whatever is posted.
   
   TearOff.c:RestoreToMenuShell - make sure that the menu is disarmed before it
   	is returned to the menu shell otherwise the events go to the
   	transient shell, which is not in use.
   
   RowColumn.c:MenuProcs - MENU_CASCADING - make sure to set the active child
   	of the menu we are cascading from and highlight the button.
   
   RowColumn.c:DoBtnEventCleanupReplay() - If the menu is not in a menu shell
   	check for a tearoff.
   
   I don't think that _XmGetActiveTopLevelMenu is returning the correct thing.
   If a pulldown is posted from a menu bar the top level menu should be the
   menu bar.  _XmGetActiveTopLevelMenu is returning the pulldown that the
   menu bar has posted.  However, you add in tearoffs and things get very
   confusing.  This needs a closer look.
TearOff.c 1.20
   date: 1998/03/01 16:44:19;  author: rwscott;  state: Exp;  lines: +10 -44
   MenuUtil.c:_XmMenuEscape() - pretty much re-write this puppy.  Now that menus
   	are setting the appropriate RC instance variables this is a little
   	easier.  It also handles an escape in tear offs now (I had been
   	wondering how you got rid of a tear-off without the help of a
   	window manager).
   
   PushBG.c:initialize() - Only install the Label menu procs if we are in a menu.
   
   RowColumn.c:MenuProcEntry() - XmMENU_BUTTON_POPDOWN - do not set the memWidget
   	if it is a TearOffButton.  Also when we set the label on the cascade
   	button set it to the memWidget.
   
   RowColumn.c:MenuProcEntry() - XmMENU_SHELL_POPDOWN - do not disarm the active
   	child if the active child is making the call.
   
   RowColumn.c:_XmOptionCallback() - protection against being call with a NULL
   	widget.
   
   TearOff.c:_XmTearOffInitiate() - Bring down the menu shell with the RC procs
   
   TearOff.c: general clean up
   
   TearOffB.c: general clean up
TearOff.c 1.19
   date: 1997/12/21 15:06:05;  author: rwscott;  state: Exp;  lines: +20 -15
   _XmRestoreTearOffToMenuShell - Use the backgroundPixmap of the transientShell
   	to display the bogus menu.  This way X takes care of the copy and
   	any expose events that happen.  Finally found the reason for the
   	RC_TearOffDirty bit!
TearOff.c 1.18
   date: 1997/12/21 14:16:58;  author: rwscott;  state: Exp;  lines: +178 -10
   This is all with respect to tearoffs.
   
   
   CascadeB.c
   
   	MenuBarEnter - Popdown the old menu only if a menushell (not torn off)
   
   	CascadePopupHandler - make sure the menu is back in its menu shell if
   		it was torn off
   
   	DelayedArm - Do not put a torn off menu back to its menushell here.
   		If the delay never times out then the menu is left in the
   		menu shell and never poped up.
   
   	CheckDisarm - If we have to popdown the menus use popdownEveryone.
   
   MenuShell.c
   
   	change_managed - If there are no managed children we pop down but, we
   	must popdown private shells different from public ones. Same goes for
   	popping up.
   
   	MenuShellPopdownOne - do not restore tear off to its toplevel shell
   	here, it just confuses popdowneveryone.
   
   	MenuShellPopdownEveryone - restore tear offs to their toplevel shells
   	here, after all the menus have been sorted out.
   
   	MenuShellPopupSharedMenuPane - Since we do not use XtPopup for menus
   	anymore we must take care of setting and un-setting of Shell_PoppedUp.
   	Not setting this was messing up <BtnDown> in push button and
   	probably other places (anywhere there was an if (Shell_PoppedUp)).
   
   PushB.c
   
   	Add some debug statements.
   
   RowColumn.c
   
   	DoBtnEventCleanupReplay - Do not call PopdownDone for a torn off menu
   
   	_XmGetActiveTopLevelMenu - Return something usefull for an active
   	tear off.
   
   TearOff.c
   
   	_XmTearOffBtnDownEventHandler - Arm the menu. Something a little
   	strange happens here, see the comments in the source.
   
   	_XmTearOffBtnUpEventHandler - DisArm the menu.
   
   	_XmTearOffInitiate - Get rid of the keyboard and pointer grabs from
   	the previous menu and turn off drag mode.
   
   	_XmAddTearOffEventHandlers - big time guess here! Add a button up
   	handler to the tear off and all of its widget children so we can
   	disarm the menu. Add a button down handler to all of the widget
   	children so we can arm the menu.
   
   	_XmRestoreTearOffToToplevelShell - Do not ungrab things here. The
   	grabs are now taken care of in the event handlers.
   	Do not reposition the shell if an event is not given.  This is due
   	the the MenuShell:change_managed call to put the menu back to the
   	toplevel shell.
   	Make sure the event handlers are in place.
   
   	_XmRestoreTearOffToMenuShell - Time for a little magic here! Ever
   	wonder how Motif keeps a copy of the tear off in the toplevel shell
   	and displays it in the menu at the same time?  Well you just take a
   	copy of the pixels in the toplevel shell before you re-parent the
   	menu and put those pixels into the shell.  Since the menu will have
   	grabs there is no way to interact with it so fake it!
   	I should be able to just set the background pixmap of the shell and
   	have X take care of the copy, stay tuned.
   	Do not unmanage the menu if it is in a private shell, they are always
   	managed.
TearOff.c 1.17
   date: 1997/12/19 01:31:01;  author: rwscott;  state: Exp;  lines: +23 -7
   CascadeB.c:_XmCascadingPopup - before posting a menu make sure that it is in
   	it menushell.
   
   CascadeB.c:CheckDisarm - If we need to popdown a menu, use MenuShellPopdownOne
   	so that the menu will get restored to its toplevel shell if torn.
   
   MenuShell.c:MenuShellPopdownDone - If the menu is a popup do not unmanage it
   	if it is an active tearoff.
   
   MenuShell.c:MenuShellPopdownOne - If the menu is an active tearoff unpost any
   	menus posted from it and put it back into its toplevel shell.
   
   TearOff.c:_XmDismissTearOff - set the TearOffActive bit to 0
   TearOff.c:_XmTearOffInitiate - set the TearOffActive bit to 1
TearOff.c 1.16
   date: 1997/12/16 21:03:41;  author: rwscott;  state: Exp;  lines: +4 -2
   _XmRestoreTearOffToMenuShell - Do not manage the menu shell when all of the
   	re-parenting is done.
   
   This fixes Jon's floating menu problem.
   
   Thanks for the callback info Jon, just what I needed.
TearOff.c 1.15
   date: 1997/12/16 03:18:07;  author: rwscott;  state: Exp;  lines: +5 -2
   CascadeB.c:StartDrag - If we are thinking of posting a menu make sure the
   	menu is put back into its menu shell if it was torn off.
   
   CascadeB.c:DelayedArm - ditto
   
   CascadeB.c:CheckDisarm - If we are thinking of un-posting a menu because
   	we are leaving the cascade button that posted it do not do it if
   	the menu is torn off.
   
   MenuShell.c:MenuShellPopdownEveryone - Do not recurse if the the shell is not
   	a menu shell, ie torn off.
   
   RowColumn.c:MenuEnter - If we are thinking of un-posting a menu, do not do
   	it if the menu is torn off.
   
   TearOff.c:_XmRestoreTearOffToMenuShell - XSync before we grab the server.
   	Do not XSync while the server is grabbed.  This was a fun one. It
   	seems that if you have the server grabbed in conjuction with
   	DEBUGSOURCES=all something gets bogged down and you get no response
   	if stderr is an xterm.  Re-direct to a file and all was ok.
   	Anyway, with the syncs and grabs altered a bit it seems okay.
TearOff.c 1.14
   date: 1997/12/15 21:54:31;  author: rwscott;  state: Exp;  lines: +25 -3
   add the [de-]activate callbacks.
   
   Does anyone know what should be in the callback structures???
   
   This is going to be difficult since on my HP box vuewm, the window manager,
   dies whenever I tear off a pulldown menu pane! So far LessTif and fvwm work
   better than Motif and vuewm when it comes to tearoffs!
TearOff.c 1.13
   date: 1997/12/15 00:08:47;  author: rwscott;  state: Exp;  lines: +25 -12
   _XmTearOffInitiate - Some protection when you tear off a popup menu, since
   	it was not posted from a CascadeButton.
   
   CreateTopLevelShell - ditto.
TearOff.c 1.12
   date: 1997/12/14 14:45:52;  author: rwscott;  state: Exp;  lines: +5 -2
   Label.c:label_menu_procs - case XmMENU_SHELL_POPDOWN -  If we have a menubar
   	with button1 and button2 and a tearoff is posted for button1 and we
   	click in button2 this routine gets called to popdown the menu for
   	button1.  Therefore if the menu to popdown is not in a menushell
   	leave it alone.
   
   MenuShell.c:MenuShellPopdownDone - If the top level widget is not a menushell
   	it must be a tearoff. In this case popdown everyone under the toplevel.
   
   TearOff.c:_XmTearOffInitiate - Preserve the value of RC_PopupPosted around the
   	call to MenuShellPopdownDone. Same as preserving the value of
   	RC_CascadeBtn.
   
   ToggleB.c:ButtonDown - Like most other places in this file when we set the
   	value for TB_IndicatorSet also set the value of TB_VisualSet.
   
   
   All of this was with tearoff/test2
TearOff.c 1.11
   date: 1997/12/12 22:26:43;  author: rwscott;  state: Exp;  lines: +29 -3
   CreateTopLevelShell - use the labelString of the cascade button for the title
   	of the torm off menu.
   
   _XmTearOffInitiate - One of the first things here is to call
   	MenuShellPopdownDone.  This sets RC_CascadeBtn() to NULL.
   	RC_CascadeBtn() is needed to get the title of the torn off shell.
   	Therefore save the RC_CascadeBtn before the popdownDone and restore
   	it afterwards.
   
   This may have been causing problems in other parts of TearOff's also since
   the button that posted the menu was being set to NULL


TearOffB.c Current rev 1.14 Last Release 1.10
TearOffB.c 1.14
   date: 1998/03/01 16:44:20;  author: rwscott;  state: Exp;  lines: +2 -27
   MenuUtil.c:_XmMenuEscape() - pretty much re-write this puppy.  Now that menus
   	are setting the appropriate RC instance variables this is a little
   	easier.  It also handles an escape in tear offs now (I had been
   	wondering how you got rid of a tear-off without the help of a
   	window manager).
   
   PushBG.c:initialize() - Only install the Label menu procs if we are in a menu.
   
   RowColumn.c:MenuProcEntry() - XmMENU_BUTTON_POPDOWN - do not set the memWidget
   	if it is a TearOffButton.  Also when we set the label on the cascade
   	button set it to the memWidget.
   
   RowColumn.c:MenuProcEntry() - XmMENU_SHELL_POPDOWN - do not disarm the active
   	child if the active child is making the call.
   
   RowColumn.c:_XmOptionCallback() - protection against being call with a NULL
   	widget.
   
   TearOff.c:_XmTearOffInitiate() - Bring down the menu shell with the RC procs
   
   TearOff.c: general clean up
   
   TearOffB.c: general clean up
TearOffB.c 1.13
   date: 1998/02/22 14:42:06;  author: rwscott;  state: Exp;  lines: +6 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
TearOffB.c 1.12
   date: 1998/02/22 01:00:57;  author: rwscott;  state: Exp;  lines: +6 -12
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
TearOffB.c 1.11
   date: 1997/11/21 18:01:18;  author: miers;  state: Exp;  lines: +4 -9
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.


Text.c Current rev 1.50 Last Release 1.46
Text.c 1.50
   date: 1998/02/22 01:00:58;  author: rwscott;  state: Exp;  lines: +3 -3
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
Text.c 1.49
   date: 1997/12/11 23:27:03;  author: u27113;  state: Exp;  lines: +23 -4
   Implement XmTextClearSelection as requested by Flemming Gram Christensen.
Text.c 1.48
   date: 1997/12/11 02:47:04;  author: rwscott;  state: Exp;  lines: +3 -3
   Same problem as TextF. The hightlight thickness was being stored in the
   shadow thickness instance variable.
Text.c 1.47
   date: 1997/12/03 13:22:05;  author: rwscott;  state: Exp;  lines: +3 -3
   _XmTextInsert - Enable the calling of the valueChanged callback.


TextF.c Current rev 1.39 Last Release 1.26
TextF.c 1.39
   date: 1998/03/13 17:43:10;  author: rwscott;  state: Exp;  lines: +8 -4
   set_values() - If the foreground or background changes just ignore the fact
   	if we are not realized, since no GC's will have been created yet and
   	more importantly we cannot create GC's before we have a window.
   
   This was reported as an alpha and an NT problem just moments ago.
TextF.c 1.38
   date: 1998/03/08 18:43:08;  author: rwscott;  state: Exp;  lines: +3 -3
   Fixes from "Alexander Mai" <st002279@hrzpub.tu-darmstadt.de>
   
   I just turned -Wall back on for myself so things like this should not so
   easily slip by. It must have got turned off in the automake upgrade.
TextF.c 1.37
   date: 1998/02/28 12:41:58;  author: rwscott;  state: Exp;  lines: +5 -4
   Use _XmHighlightBorder/_XmUnhighlightBorder instead of calling the methods
   directly.  The previously reported wacky behaviour with this was my problem.
   It was part of a work around for about LessTif 0.55 or so.
TextF.c 1.36
   date: 1998/02/27 00:20:44;  author: rwscott;  state: Exp;  lines: +11 -2
   expose - Something is wacked here!  If I use _XmUnhighlightBorder the
   	proc never even gets called! However if I invoke the method directly
   	it works????
TextF.c 1.35
   date: 1998/02/22 01:01:00;  author: rwscott;  state: Exp;  lines: +22 -7
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
TextF.c 1.34
   date: 1998/02/14 12:37:05;  author: rwscott;  state: Exp;  lines: +239 -217
   patch from Paul Flinders <paul@dawa.demon.co.uk>. I will let him
   describe it....
   
   Currently the textField widget only calls its ModifyVerify callback in
   a very limited number of cases. This means that applications which do
   (e.g.) password entry break because they don't see deletes in the
   widget.
   
   The following patches (against the 26 Jan snapshot) provide a
   "unified" text modify function which can be called from anywhere which
   wants to alter the value.
TextF.c 1.33
   date: 1998/02/10 23:10:31;  author: rwscott;  state: Exp;  lines: +3 -3
   activate - Pressing return in a TextF that is part of a pre-defined dialog
   	passes the event up to the "Box" ancestor.  This is not only a
   	MessageBox but a SelectionBox as well.
   
   This makes the return key in xdir behave as expected but may screw up
   FileSelectionBox's as a result.  I have not checked yet (scrambling to
   relink everything)
TextF.c 1.32
   date: 1998/01/28 03:56:33;  author: rwscott;  state: Exp;  lines: +3 -2
   expose - erase the cursor before the DrawAll otherwise a few pixels of the
   	text get over written.
TextF.c 1.31
   date: 1998/01/20 22:55:05;  author: u27113;  state: Exp;  lines: +17 -2
   i18n fix by Shinichi Takanami
   
   INSTALL file updated, converted to HTML.
   	Use XmHTML to view if you're a real LessTif lover.
TextF.c 1.30
   date: 1998/01/13 03:11:57;  author: rwscott;  state: Exp;  lines: +3 -2
   CursorDraw - erase the old cursor before drawing the new one.  This cleans up
   	some of the pixel dust that gets left around.
TextF.c 1.29
   date: 1998/01/02 13:59:55;  author: rwscott;  state: Exp;  lines: +5 -2
   The help action should walk up the widget tree looking for an ancestor with
   a help callback, like the one from Primitive.  Therefore use the one from
   Primitive.
TextF.c 1.28
   date: 1997/12/11 01:37:14;  author: rwscott;  state: Exp;  lines: +8 -16
   initialize - TextF_TextWidth(w) was not being set if the XmNvalue was
   	specified during create.  This was messing up delete_previous_char
   	if it was the first thing done to the text. (textf/test6)
TextF.c 1.27
   date: 1997/12/11 00:16:13;  author: rwscott;  state: Exp;  lines: +5 -3
   The default highlight_thickness resource was being saved into the
   shadow_thickness resouce. This was killing the shadow of Mosaic's
   TextField widgets.


TextOut.c Current rev 1.41 Last Release 1.38
TextOut.c 1.41
   date: 1997/12/05 02:35:57;  author: rwscott;  state: Exp;  lines: +4 -2
   XToPos - fix from Andreas for a past_end problem.
TextOut.c 1.40
   date: 1997/12/04 00:51:25;  author: rwscott;  state: Exp;  lines: +4 -4
   Fixes as suggested by Andreas from the list.  Dealing with XmString
   components.
TextOut.c 1.39
   date: 1997/11/22 05:31:10;  author: miers;  state: Exp;  lines: +4 -3
   MacrosI.h: Add a macro for GrabKind in Shell.
   
   RowColumn.c: Alter the menuPost import operator to use _XmMapBtnEvent.
   
   TextOut.c: *One* of Andreas' patches.  I don't know enough about the
   other one.
   
   Todo: nedit (latest version) has a popup menu that they are using
   XtManageChild() *AND* XtPopup(x, XtGrabNonexclusive) on.  This, needless
   to say, doesn't work with our grab mechanics very well.  Motif somehow
   copes.  Sigh.


TextStrSo.c Current rev 1.15 Last Release 1.13
TextStrSo.c 1.15
   date: 1998/02/22 01:01:02;  author: rwscott;  state: Exp;  lines: +3 -2
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
TextStrSo.c 1.14
   date: 1997/12/12 13:09:35;  author: rwscott;  state: Exp;  lines: +14 -3
   _XmTextConvertSelection - I think we need to make a copy of the value here. In
       ml if you select part of a message and try to paste it into another window
       you get a segfault in free(). It would appear that Xt is free'ing
       the contents of value.


ToggleB.c Current rev 1.28 Last Release 1.21
ToggleB.c 1.28
   date: 1998/03/01 19:22:13;  author: rwscott;  state: Exp;  lines: +2 -65
   ToggleB[G].c - general clean up
   
   MenuUtil.c:_XmMenuEscape() - watch out for gadgets when determining what type
   	of menu we are in.
   
   Just say NO, to Gadgets! (I think they are more of a pain than they are worth)
ToggleB.c 1.27
   date: 1998/02/28 18:42:04;  author: rwscott;  state: Exp;  lines: +63 -2
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
ToggleB.c 1.26
   date: 1998/02/25 05:31:06;  author: rwscott;  state: Exp;  lines: +30 -41
   Clean toggleButton out of its intimate knowledge of the menu system.
   Each of the button types seem to have their own little tests when it comes
   to menus, all of which are getting concentrated in RowColumn for a more
   consistent treatment of the menus.
ToggleB.c 1.25
   date: 1998/02/22 21:42:28;  author: rwscott;  state: Exp;  lines: +22 -2
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
ToggleB.c 1.24
   date: 1998/02/22 14:42:07;  author: rwscott;  state: Exp;  lines: +10 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
ToggleB.c 1.23
   date: 1997/12/14 14:45:53;  author: rwscott;  state: Exp;  lines: +5 -2
   Label.c:label_menu_procs - case XmMENU_SHELL_POPDOWN -  If we have a menubar
   	with button1 and button2 and a tearoff is posted for button1 and we
   	click in button2 this routine gets called to popdown the menu for
   	button1.  Therefore if the menu to popdown is not in a menushell
   	leave it alone.
   
   MenuShell.c:MenuShellPopdownDone - If the top level widget is not a menushell
   	it must be a tearoff. In this case popdown everyone under the toplevel.
   
   TearOff.c:_XmTearOffInitiate - Preserve the value of RC_PopupPosted around the
   	call to MenuShellPopdownDone. Same as preserving the value of
   	RC_CascadeBtn.
   
   ToggleB.c:ButtonDown - Like most other places in this file when we set the
   	value for TB_IndicatorSet also set the value of TB_VisualSet.
   
   
   All of this was with tearoff/test2
ToggleB.c 1.22
   date: 1997/11/21 04:32:31;  author: miers;  state: Exp;  lines: +33 -4
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


ToggleBG.c Current rev 1.26 Last Release 1.18
ToggleBG.c 1.26
   date: 1998/03/01 19:22:14;  author: rwscott;  state: Exp;  lines: +12 -98
   ToggleB[G].c - general clean up
   
   MenuUtil.c:_XmMenuEscape() - watch out for gadgets when determining what type
   	of menu we are in.
   
   Just say NO, to Gadgets! (I think they are more of a pain than they are worth)
ToggleBG.c 1.25
   date: 1998/02/28 18:42:05;  author: rwscott;  state: Exp;  lines: +61 -2
   The last of the menu clean up.  All menu related functions are now in RC and
   invoked through the RC_Menu class procs.  The menu item controls now install
   a version of the label menu procs tailored for them.  The menu code, in RC,
   can now highlight/unhighlight a menu control by a call to the label menu
   proc of the control.  All that is left is to get rid of several hundred lines
   of #if 0'ed out code.
   
   Now, back to keyboard traversal of menus......
ToggleBG.c 1.24
   date: 1998/02/22 21:42:29;  author: rwscott;  state: Exp;  lines: +22 -2
   The rest of the Label[G] menu procs have been moved over to RowColumn.  There
   are still some direct MSClass calls left in some of the buttons though.
ToggleBG.c 1.23
   date: 1998/02/22 14:42:08;  author: rwscott;  state: Exp;  lines: +10 -2
   FileSB.c - shrink the file list width calculation by 1 pixel. Some of the
   	trailing '/' was showing up in some cases.
   
   The rest is a result of moving the XmMENU_BUTTON proc from Label[G] to
   RowColumn.  RowColumn is now validating the button events. The Label[G]
   MENU_BUTTON procs now just print a warning and return False. Let me know
   if you see this.
ToggleBG.c 1.22
   date: 1998/02/22 01:01:03;  author: rwscott;  state: Exp;  lines: +8 -26
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......
ToggleBG.c 1.21
   date: 1998/02/21 01:50:13;  author: rwscott;  state: Exp;  lines: +10 -2
   With this keyboard traversal of menus should be possible. Feedback welcomed!
   
   CascadeB[G].c:ArmAndActivate() - If we post a submenu from a cascade button
   	in a menubar arm the first item in the menu. (Needs to be smarter
   	and arm the first active menu control)
   
   RowColumn.c - change the default radio behaviour back to False. This is wrong
   	according to misc/test16 but until we deal with it in other places
   	it messes up a bunch of toggle buttons in menus. See mgdiff->options
   	for an example.
   
   MenuUtil.c - Write all of the menu traversal handlers.....
   
   ToggleBG.c:[Enter|Leave]Window() - Do not insist on being in DragMode since
   	during keyboard traversal we are not.
ToggleBG.c 1.20
   date: 1998/01/28 20:12:34;  author: u27113;  state: Exp;  lines: +4 -4
   test/Xm/*/Makefile.am : be able to build with 2.0 library as well.
   
   working.html : add reference to BRL/CAD 4.4 which is reported to work.
   
   lib/Xm/(Gadgets) : one pixel sensitivity fixes by Gilles Seguin.
   	+ a new test in test/Xm/arrowbg for it.
   
   CURRENT_NOTES : refer to Xinvest as a demo for 2.0 PanedWindow.
   
   Paned* : the year hasn't been 1995 for a long time. Copyright changed.
ToggleBG.c 1.19
   date: 1997/11/21 04:32:32;  author: miers;  state: Exp;  lines: +33 -4
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


TravAct.c Current rev 1.7 Last Release 1.5
TravAct.c 1.7
   date: 1998/03/07 01:10:24;  author: rwscott;  state: Exp;  lines: +6 -4
   Okay, with this nedit seems fine _IFF_ run under LessTif's mwm. If run from
   fvwm everything seems fine _except_ you cannot enter text.  Pretty lame for
   an editor I know but I cannot figure out what the difference is.
   
   If only I had a man page for mwm maybe I would switch :)
TravAct.c 1.6
   date: 1998/03/06 22:55:52;  author: rwscott;  state: Exp;  lines: +6 -4
   Manager.c:_XmAcceleratorHandler - add UngrabKeyboard/UngrabPointer calls in
   	here since we get here as the result of an XtGrabKey.
   
   
   One of the problems with accelerators is that we install the XtGrabKey to
   get notification of the event.  When this notification happens the server
   generates a FocusOut event. We pick this up in _XmTrackShellFocus but are
   ignoring the mode of NotifyGrab.  Similarly when we now ungrab we pick this
   up but again are ignoring the mode of NotifyUngrab.  Somewhere in these 2
   focus events we have to save where the focus was before the grab and then
   put it back after the grab.
   
   Any help gratiously accepted.
   
   		Rick


Traversal.c Current rev 1.23 Last Release 1.22
Traversal.c 1.23
   date: 1998/02/15 15:07:33;  author: rwscott;  state: Exp;  lines: +7 -4
   Change the debug stuff so that DEBUGSOURCES=Traversal.c gives us the normal
   debug trace without the tree dumping.  To enable tree dumping set the
   define that is still in Traversal.c


Vendor.c Current rev 1.33 Last Release 1.28
Vendor.c 1.33
   date: 1998/03/13 22:42:14;  author: u27113;  state: Exp;  lines: +16 -4
   Vendor.c : now it can work for 2.0 too.
   
   FontList.c : warning removed.
   
   lib/Xm-2.0/Makefile.am : pick up the lib/Xm version instead of lib/Xm-2.0
   	of Vendor.c
Vendor.c 1.32
   date: 1998/02/14 17:29:36;  author: rwscott;  state: Exp;  lines: +58 -9
   ddd is destroying an XmDialogShell widget called init_shell.  This widget
   gets put on the grab list.  However when this widget is destroyed it is
   not being taken off the grab list because it is not considered to be
   a subclass of Vendor!
   
   see the comments in Vendor.c::LTRemoveGrabCallback
Vendor.c 1.31
   date: 1998/02/02 14:57:11;  author: u27113;  state: Exp;  lines: +6 -4
   xmdipmon has a strange way of exiting. I.e. it is the only app I know
   that uses the X11R6 way of doing this.
   
   Side effect #1 : we printed a message from BaseClass.c about not being
   able to pop ExtNode. Removed that in case of widget being_destroyed.
   
   Side effect #2 : we got a NULL pointer that we tried to dereference in
   Vendor.c's destroy(). Fixed that too.
Vendor.c 1.30
   date: 1997/12/12 18:34:51;  author: rwscott;  state: Exp;  lines: +15 -2
   geometry_manager - If mgs is correct a child may ask for a change of x/y.
   	So do not deny the geometry request based on this alone.
Vendor.c 1.29
   date: 1997/11/21 04:32:34;  author: miers;  state: Exp;  lines: +5 -7
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


VirtKeys.c Current rev 1.6 Last Release 1.5
VirtKeys.c 1.6
   date: 1997/11/21 18:01:19;  author: miers;  state: Exp;  lines: +3 -3
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.


Visual.c Current rev 1.9 Last Release 1.5
Visual.c 1.9
   date: 1998/01/06 23:51:49;  author: miers;  state: Exp;  lines: +3 -3
   Add patches from Paul Flinders for Xpm handling of pixmaps.
Visual.c 1.8
   date: 1997/11/22 18:37:13;  author: miers;  state: Exp;  lines: +61 -240
   MacrosI.h: Add macros for Core fields when we want them not as functions.
   
   Primitive.c: I accidentally removed one of the pixmap default functions.
   
   Visual.c: Gilles Seguin tells me that "unspecified_pixmap" is a valid string
   value for the various pixmaps -- it just means XmUNSPECIFIED_PIXMAP.
Visual.c 1.7
   date: 1997/11/21 18:01:21;  author: miers;  state: Exp;  lines: +3 -3
   Shadow.c: Highlights are supposed to use XFillRectangle to get the proper
   highlight pixmap effects.
   
   DrawingArea.c, Gadget.c, Manager.c, Primitive.c, RowColumn.c: semantics
   of widget_navigable weren't quite right.  The exclusivity of the shell
   is only important if the widgets are TAB_NAVIGABLE.
   
   Gadget.c, Primitive.c: When FOCUS_OUT, set HaveTraversal to False, not True
   (focus_change).
   
   VirtKeys.c: patch from the list.
   
   Primitive.c, Manager.c, Visual.c: The function is supposed to be named
   _XmClearBGPixmap(), not _XmClearBGPixmapName().
   
   TearOffB.c: warning removal from the event loop.  I gotta compile on linux
   more often.
Visual.c 1.6
   date: 1997/11/21 04:32:35;  author: miers;  state: Exp;  lines: +613 -3
   Add in string to pixmap converters.  Thanks to Gilles Seguin for the
   suggestions.
   
   Gadget.c, Manager.c, Primitive.c, Vendor.c: Add the call to
   _XmRegisterPixmapConverters().
   
   Manager.c, Primitive.c: There's a really nasty thing that setting the
   backgroundPixmap can cause.  See the comments in initialize() around
   _XmGetBGPixmapName().
   
   MapEvent.c: A request from Alex Mai for <strings.h> here.
   
   PushB.c, PushBG.c, ToggleB.c, ToggleBG.c: All of these have a backgroundGC
   member.  For correct visuals, these need to include backgroundPixmap when
   the GC's are created.  Try
   'test/Xm/pushbutton/test1 -xrm "*.backgroundPixmap: slant_left"
   for details.
   
   Visual.c: Add a bunch of pixmap converters.


World.c Current rev 1.3 Last Release 1.2
World.c 1.3
   date: 1998/02/22 01:01:04;  author: rwscott;  state: Exp;  lines: +11 -56
   Mostly class structure synchronization, get rid of un-used methods, stub out
   methods that we are supposed to have, get the compress flags right....
   
   A couple of fixes to note.  BulletinBoard was not un-drawing its shadows
   when resized bigger, and the ModifyVerify patch from a few days ago was
   segfaulting on textf/test4.
   
   Now back to the menu system......


XmString.c Current rev 1.16 Last Release 1.12
XmString.c 1.16
   date: 1998/02/05 23:36:37;  author: u27113;  state: Exp;  lines: +15 -2
   Fix some memory leaks.
XmString.c 1.15
   date: 1998/01/17 14:56:32;  author: u27113;  state: Exp;  lines: +29 -12
   configure* : OS/2 updates from Michael Holzapfel.
   	EMX (a GCC/POSIX runtime for OS/2) is now recognised.
   	Not sure if this is complete.
   
   lib/Xm/XmString.c :
   	Fix for core dump from Maciej MOCHOL <mmochol@elka.pw.edu.pl>
XmString.c 1.14
   date: 1997/12/18 23:25:45;  author: u27113;  state: Exp;  lines: +3 -3
   Add tests and warnings, hope to solve a problem reported by
   scott hutinger <srh@skyping.mprojects.wiu.edu> in the JDK port
   for PowerPC.
XmString.c 1.13
   date: 1997/12/04 00:51:26;  author: rwscott;  state: Exp;  lines: +6 -6
   Fixes as suggested by Andreas from the list.  Dealing with XmString
   components.


XmXpm.c Current rev 1.3 Last Release 1.1
XmXpm.c 1.3
   date: 1997/08/19 19:29:26;  author: miers;  state: dead;  lines: +0 -0
   More code reorg.
   
   1) Moved all the Xme functions to the 2.0 tree.  Something needs to be
   done about the headers, though.
   
   2) If LESSTIF_PRODUCTION is defined, then the Editres handler and the
      pixmap extensions aren't built.  I'd like to move these to another
      place (e.g., extensions/) but it's so much trouble to hack configure
      that I'm putting it off.
   
   3) Add an Editres for R5.
XmXpm.c 1.2
   date: 1997/07/12 18:37:10;  author: miers;  state: Exp;  lines: +1242 -862
   Indenting done -- whew.


Executive Summary
Of 105 files, 71 changed, and 34 had no change

File            Current Rev. Last Release
.indent.pro     1.1          1.1    No Change
ArrowB.c        1.17         1.12   
ArrowBG.c       1.12         1.9    
AtomMgr.c       1.3          1.3    No Change
BaseClass.c     1.9          1.8    
BulletinBoard.c 1.21         1.19   
Cache.c         1.7          1.7    No Change
CascadeB.c      1.80         1.57   
CascadeBG.c     1.74         1.60   
Command.c       1.9          1.8    
CutPaste.c      1.4          1.4    No Change
DebugUtil.c     1.25         1.21   
DefaultProcs.c  1.9          1.5    
DragIcon.c      1.7          1.7    No Change
DragOverS.c     1.8          1.7    
DragUnder.c     1.2          1.2    No Change
DrawingArea.c   1.20         1.19   
DrawnB.c        1.23         1.20   
DropSMgr.c      1.15         1.14   
DropTrans.c     1.8          1.7    
ExtObject.c     1.3          1.3    No Change
FileSB.c        1.24         1.21   
FontList.c      1.10         1.7    
Form.c          1.106        1.103  
Frame.c         1.34         1.33   
Gadget.c        1.11         1.7    
GadgetUtil.c    1.6          1.4    
GeoUtils.c      1.18         1.16   
Hash.c          1.2          1.2    No Change
ImageCache.c    1.9          1.8    
LTCvt.c         1.4          1.2    
LTEditres.c     1.6          1.1    
LTV5Editres.c   1.2          1.2    No Change
LTV6Editres.c   1.2          1.2    No Change
LTXpm.c         1.3          1.2    
LTfnmatch.c     1.2          1.2    No Change
LTglob.c        1.3          1.3    No Change
Label.c         1.58         1.45   
LabelG.c        1.51         1.40   
List.c          1.38         1.31   
MainW.c         1.26         1.24   
Makefile.am     1.9          1.9    No Change
Makefile.in     1.15         1.13   
Manager.c       1.46         1.37   
MapEvent.c      1.10         1.6    
MenuShell.c     1.65         1.52   
MenuUtil.c      1.26         1.10   
MessageB.c      1.20         1.19   
Messages.c      1.3          1.3    No Change
Mwm.c           1.2          1.2    No Change
Obsolete.c      1.2          1.2    No Change
PanedW.c        1.32         1.31   
Primitive.c     1.27         1.24   
Protocols.c     1.3          1.2    
PushB.c         1.34         1.22   
PushBG.c        1.33         1.19   
RCUtils.c       1.72         1.68   
ReadImage.c     1.1          1.1    No Change
Region.c        1.3          1.2    
RepType.c       1.3          1.3    No Change
ResConvert.c    1.19         1.15   
ResInd.c        1.4          1.4    No Change
RowColumn.c     1.138        1.103  
Sash.c          1.10         1.9    
Scale.c         1.23         1.22   
Screen.c        1.10         1.9    
ScrollBar.c     1.21         1.16   
ScrolledW.c     1.68         1.67   
Selection.c     1.1          1.1    No Change
SelectionBox.c  1.24         1.20   
SeparatoG.c     1.7          1.5    
Separator.c     1.6          1.4    
Shadow.c        1.10         1.8    
ShellExt.c      1.3          1.2    
Simple.c        1.13         1.10   
TearOff.c       1.23         1.10   
TearOffB.c      1.14         1.10   
Text.c          1.50         1.46   
TextF.c         1.39         1.26   
TextIn.c        1.26         1.26   No Change
TextOut.c       1.41         1.38   
TextStrSo.c     1.15         1.13   
ToggleB.c       1.28         1.21   
ToggleBG.c      1.26         1.18   
TrackLoc.c      1.2          1.2    No Change
Transltns.c     1.4          1.4    No Change
TravAct.c       1.7          1.5    
Traversal.c     1.23         1.22   
UniqueEvent.c   1.3          1.3    No Change
VaSimple.c      1.2          1.2    No Change
Vendor.c        1.33         1.28   
VirtKeys.c      1.6          1.5    
Visual.c        1.9          1.5    
World.c         1.3          1.2    
XmIm.c          1.4          1.4    No Change
XmOS2.def.dist  1.1          1.1    No Change
XmOS2.def.orig  1.2          1.2    No Change
XmStrDefs.c     1.2          1.2    No Change
XmString.c      1.16         1.12   
XmXpm.c         1.3          1.1    
Xmos.c          1.12         1.12   No Change
alloca.c        1.2          1.2    No Change
inlines.in      1.3          1.3    No Change
misc.c          1.6          1.6    No Change
mkinline.c      1.3          1.3    No Change
