[Libreoffice-ux-advise] [Bug 141747] CROSS-REFERENCE: Give warning, if you delete a target of a cross-reference

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Tue Mar 1 08:41:07 UTC 2022


https://bugs.documentfoundation.org/show_bug.cgi?id=141747

--- Comment #6 from Christian Lehmann <christianw_lehmann at arcor.de> ---
(In reply to Christian Lehmann from comment #5)
> (In reply to Heiko Tietze from comment #4)
> > Coming back to this, sorry for the delay. My test scenario is a references
> > to a figure showing the page number. Now I cut the figure and paste it
> > somewhere else. The reference's link remains intact but the page number is
> > not shown anymore. 
> > 
> > But besides of this bug, how would you know whether the target is to be
> > pasted or deleted? I mean the suggested warning would show up anyway.
> > 
> > The actual problem of saving/printing a document with lost references is
> > clear to me. And if dealing with cut/delete while editing is not possible we
> > could show the infobar on opening.
> 
> Heiko, I am not sure that the distinction between cut out and delete is
> actually a problem. I have a test file with a numbered object and a
> reference to it. If I cut out the numbered object, the reference is changed
> to 'Error: Reference source not found'. As soon as I paste the object
> somewhere, the reference is updated.
> 
> There are two points at which the software could note the difference:
> a) Cutting out is a different operation from deletion. Put out a warning
> only if a numbered object to which there are references is deleted.
> b) If the user launches a Save operation, check if there are instances of
> 'Error: Reference source not found', and if so, warn the user and offer
> 'Cancel' (of the Save operation).

However, both of these warnings make sense only if the user can do a Find on
instances of 'Error: Reference source not found', which is a pending
desideratum, anyway.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Libreoffice-ux-advise mailing list