On Thu, Jan 17, 2002 at 03:18:44PM +1000, Allan Rae wrote:

> Yeah, this is what insure++ calls a FREE_BODY where libXpm is freeing
> part of the buffer it malloced.  This seems to be okay in that case.

it's not, it's trying to strcasecmp the name string with a string at 0xb

> Can you tell njamd to ignore certain libraries or something?  (this
> would help me too)

dunno ...

> This would hide the problem nicely but I think we should instead make
> sure that when we are exporting we should probably have
> InsetInclude::latex() not only load the file if it isn't already but

eek, a view->dvi has to load 20 chapters ??

> > insetgraphics still needs a lot of work IMHO, but I don't know who's going to do 
>it. I had
> > a trawl of freshmeat, and it looks like imlib2 and libafterimage are our best 
>choices for
> > implementing scaling etc. At least of one these offers line-by-line decoding, 
>which we can do
> > in an xforms idle callback I think.
> 
> I think Baruch was hoping to use anything that was available but it
> would be preferable that the same toolkit was used whether scaling was
> needed or not.

what do you mean ?

regards
john

-- 
"Hey, we could invent a programming paradigm where the program is expressed as
a series of statements to be executed in a fixed order."
        - Khendon

Reply via email to