Conference bulova::decw_jan-89_to_nov-90

That ought to work, although you don't need the char * type cast.  I think the
problem must be in the "Use s for whatever" code.  Can you give an example of
some of the "whatevers" that are causing trouble?  Do they involve any other
calls to compound string routines?

--PSW

Here's an example from the code:


void DWS_UpdateHumidity(char *hsb,char *hrb,char *hdb)
{
DwtCompString hs,hr,hd;


hs = DwtLatin1String(hsb);
hr = DwtLatin1String(hrb);
hd = DwtLatin1String(hdb);

SetLabel(cb_h_set,hs);
SetLabel(cb_h_act,hr);
SetLabel(cb_h_dev,hd);

XtFree((char *)hs);
XtFree((char *)hr);
XtFree((char *)hd);

}



hsb, hrb and hdb are all strings created by sprintf() and passed to this
function.

SetLabel is a macro:

#define SetLabel(w,t)           DWS_SetArg(W_list[(w)],DwtNlabel,(t))

and here is DWS_SetArg()



void DWS_SetArg(Widget w, char *resource, char *value)
{
Arg al[1];

XtSetArg(al[0], resource, value);
XtSetValues(w, al, 1);
}

Please post the code for SetLabel.

--PSW

It's a macro:

#define SetLabel(w,t)           DWS_SetArg(W_list[(w)],DwtNlabel,(t))



and here is DWS_SetArg()



void DWS_SetArg(Widget w, char *resource, char *value)
{
Arg al[1];

XtSetArg(al[0], resource, value);
XtSetValues(w, al, 1);
}



John

Well, that's the way it's supposed to work, to the best of my knowledge.  It
doesn't look like your code is dropping any compound strings on the floor.
This sounds like a memory leak either in XtFree or in the label widget.  I
suggest QARing a simple complete example program that illustrates the problem.

Thanks Paul.

I haven't had time to QAR this yet (been out of town), but today I did get
to isolate it. It's in the call to the SetLabel macro, which is as follows:

#define SetLabel(w,t)           DWS_SetArg(W_list[(w)],DwtNlabel,(t))

DWS_SetArg is this:

void DWS_SetArg(Widget w, char *resource, char *value)
{
Arg al[1];

XtSetArg(al[0], resource, value);
XtSetValues(w, al, 1);
}


The widget in question is a pushbutton (which I used because of it's 
nice look!. I don't use it [them] as a pushbutton, just a display
element to show the current values of a dynamic setpoint).

Anyway, it appears the widget is eating up memory for it's label name. 

I suspect that on every call to XtSetValues for the DwtNlabel, it simply
allocates more memory without freeing previously allocated "label name"
memory.  Could the pushbutton widget owner check on this?

I will QAR it when I get together a smaller program to demonstrate it.

I'm going to try switching to another widget (label?) to see what happens...

John

I switched to using a label widget. Same results.

BTW - It sure is easy changing this kind of thing in UIL. Literally
changing all the appropriate "push_button" object names to "label"
and then adding one other resource value:  border_width = 2;

John

ALl right, so about the only work-around I can figure is to free the label
storage myself. 

Anyone have the struct definition for  a label widget?


John