On Thu, 17 Jan 2002, John Levon wrote: > 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
Then njamd is complaining about something that is suppressed within insure++ (since it isn't in the code I'm checking). > > 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 ?? It does this anyway since it has to generate the latex from the lyx files. On the other hand we don't really want to have to render those files if we can get away without doing so -- what happens now. So if we could just get our hands on a minibuffer some other way we'd be right. > > > 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 ? Use the same toolkit/library to do the conversion and the scaling if possible. And don't tie ourselves to any particular toolkit/library. Allan. (ARRae)
