[Xastir-Dev] Short list, stable release, then Xastir-2 development?

[J. Lance Cotton]

Curt Mills, WE7U wrote:
> On Thu, 20 Mar 2003, J. Lance Cotton wrote:
> 
> 
>>         default:
>>             fprintf(stderr,"Illegal parameter (%d) passed to
>>GPS_operations function!\n", input_param);
>>             gps_operation_pending = 0;  // We're done
>>             return(NULL);
>>             break;
>>     }   // End of switch
>>
>>tells me that input_param is 0 when this function is called. This is
>>coming from the XtPointer clientData. Beyond that, it appears that the
>>callback function is being called with the right data (between 1 and 3,
>>inclusive).
> 
> 
> So the printf to STDERR is showing you a '0' I presume.  Actually
> the parameter has to be between 1 and 6 inclusive in order to avoid
> the switch's default clause.  The other three clauses are for
> possible GPS upload functions that I/we might add later.
> 
> The string value should have been set by the callback functions from
> the code that created the menus, so perhaps there's a difference
> with how your menus are sending the values to the code and how mine
> are?  Are you using LessTif, Motif, or OpenMotif?  I'm using
> OpenMotif here.

I saw that the only 'possible' values were 1 through 6 (really through 
3), but yes, I am getting a '0' in there. I am using LessTif (with SuSE 
8.1). All of the other menus are fine. In fact, my right-clicking with 
num-lock on is now working (as of about a month ago)!


-- 
J. Lance Cotton, KJ5O
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat 
the cookies.