Version: 7.0.0.3 (x64) Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded AFAIK, at present you cannot insert a cross-reference DIRECTLY to an image in a document: IME, you have to set the cross-reference indirectly on the same page/frame containing the image. And lists of illustrations can be very long – requiring a lot of preliminary spadework to set the references! SUGGESTION: Allow images to appear as a new category under "FIELDS > CROSS REFERENCES > TYPE", with the names of the images appearing in the "Selection" pane. Thus, cross-references could be inserted directly, as they are for headings, for example.
At least a workaround: If you insert an image with a caption, you can insert a cross-reference to that caption (Type is "Figure"). Does this solve your problem? => NEEDINFO
(In reply to Dieter from comment #1) > At least a workaround: If you insert an image with a caption, you can insert > a cross-reference to that caption (Type is "Figure"). Does this solve your > problem? > > => NEEDINFO Yes. That's a possibility. But in illustrated books of moderate length, for example, there can be scores of images, and with larger works, 100-200 or more. To create a TOC, you need to add all those reference marks, then the cross references themselves: very time-consuming.
(In reply to R. Green from comment #2) > Yes. That's a possibility. But in illustrated books of moderate length, for > example, there can be scores of images, and with larger works, 100-200 or > more. To create a TOC, you need to add all those reference marks, then the > cross references themselves: very time-consuming. I only wanted to show a kind of workaround. I don't know, if it is possible to implement your enhancement request. I hope, somebody else can help.
All cross references are text based, if you remove the table heading you wont be able to find it. And I doubt that we can change this and figure out what type of object is behind the binary data of a bitmap. UX-wise we run into trouble if images are recognized without a caption but other objects not. All or nothing.
I was looking for something slightly different, but it could be probably "merged" into this enhancement. Writing manuals, it often happens to insert repetitive images, such as CAUTION or WARNING ISO signs, and others. It would be useful to set them as Cross Reference, in order to recall them (meaning the whole image, usually anchored as character) all the times. The difference respect to inserting the same image every time, is that you (or the client) may change your (his) mind: having such a feature, you just have to change the first occurrence of the image (the one which SETs the Xref) and all the other in the whole manual would change accordingly! Moreover, I hope and guess that LO is so smart to not embed n times the same picture, if and when it's repeated, but making it as a Xref would probably optimize that too (if needed ;). If I've been not clear, please ask.
(In reply to Gabriele Ponzo from comment #5) > Writing manuals, it often happens to insert repetitive images, such as > CAUTION or WARNING ISO signs, and others. It would be useful to set them as > Cross Reference, in order to recall them (meaning the whole image, usually > anchored as character) all the times. > > The difference respect to inserting the same image every time, is that you > (or the client) may change your (his) mind: having such a feature, you just > have to change the first occurrence of the image (the one which SETs the > Xref) and all the other in the whole manual would change accordingly! I understand your idea, but I won't call this a cross reference, because you don't have a reference something else.
> (In reply to Gabriele Ponzo from comment #5) > > Writing manuals, it often happens to insert repetitive images, such as > > CAUTION or WARNING ISO signs, and others. It would be useful to set them as > > Cross Reference, in order to recall them (meaning the whole image, usually > > anchored as character) all the times. > > > > The difference respect to inserting the same image every time, is that you > > (or the client) may change your (his) mind: having such a feature, you just > > have to change the first occurrence of the image (the one which SETs the > > Xref) and all the other in the whole manual would change accordingly! > > I understand your idea, but I won't call this a cross reference, because you > don't have a reference something else. (In reply to Dieter from comment #6) You have it: the reference image (where you SET the xRef) and all the recalls to it (where you Insert the xRef), exactky as I do tons of times for definitions and acronyms.
heko, you've added keyword needsDevAdvice with comment 4. Is it necessary to add an email address together with this keyword. We have no input from any developer since more than two years, so I'd like to ask.