Right, next place to go is to src/uipp/widgets/Stepper.c:Button[Increase|Decrease] at which point things seem to get a little confusing.
On 09-Dec-99 at 05:49, David L. Thompson ([EMAIL PROTECTED]) wrote: > Okay, > > I didn't do any wacky builds. Pretty straight forward (CVSMake > followed by configure). > > I test this, and the arrows are doing what they are supposed to > Enter, Arm, Activate 000, Disarm, and Leave. So it looks like it must > be in the Callback somewhere (right?) > > On Friday, I may have some time to devote to trying to get this and > the Control Panel problem looked at. > > David > > >David, I think I have addressed all of the "usability" concerns from your > >recent list that I can reproduce. Like I have said in the past, activating > >the arrow buttons on the Integer Interactor seems fine for me, so I'm > >going to need > >a little help with this one. I suspect if we find out what is going on for > >one of these the rest will fall into place. So here goes..... > > > >Hopefully you haven't specified any of the wacky build flags for LessTif. > >I think the one that you must _not_ have specified is > >--enable-production. If by chance you did, re-configure and build _without_ > >the --enable-production flag. > >Okay, start dx with > > > >DEBUGSOURCES=ArrowB.c dx -edit > >Drop down an integer interactor and double click on it > >You should see a couple of lines of LessTif debug output on stderr. So far > >there should be a couple of lines indicating a set_values has been > >done on both > >of the arrows. Now activate one of the arrow buttons. You should get an > >indication of .... well, it's easier to show you.... > > > >XmArrowButton left: EnterWindow > >XmArrowButton left: LeaveWindow > >XmArrowButton left: EnterWindow > >XmArrowButton left: Arm > >XmArrowButton left: Activate 000 > >XmArrowButton left: Disarm > >XmArrowButton left: LeaveWindow > > > >The same sort of thing should show up for the right arrow, except it's > >name will be right not left. If we are getting this far we can move on to > >the next step. Now this is what you could call "remote debugging" :) > > > > > >If you've got some time on your hands try running DEBUGSOURCES=all for an > >indication of how much LessTif code this thing is actually ploughing > >through. > > ............................................................................. > David L. Thompson The University of Montana > mailto:[EMAIL PROTECTED] Computer Science Department > http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812 > Work Phone : (406)257-8530
