Andrew Douglas Pitonyak wrote:
Have been poking around the LO code today trying to decide where I might put break points to help in tracking this. Looks like this occurs (for my sample) when auto-save kicks in, so I may place a break point in the auto save code and then start stepping through it to see if anything obvious looks wrong.
Hi Andrew, so the high-level object handling images in Writer is SwGrfNode (sw/source/core/graphic/ndgrf.cxx) It builds upon the GraphicManager framework, to be found around here: (svtools/source/graphic/grfmgr2.cxx) Note that saving graphics is a bit nasty, since no objects are handed around, but urls containing image checksums - grep for mxGraphicResolver in xmloff, mxGraphicResolver->resolveGraphicObjectURL( aURL ) puts that into the package (and may fail in your case - for checksums subtly changing, or graphics ceasing to be registered with their checksum at the GraphicManager). HTH, -- Thorsten
Attachment:
pgpxiiwbZzILs.pgp
Description: PGP signature