https://bugs.documentfoundation.org/show_bug.cgi?id=38760
--- Comment #30 from Wolfgang Jäger <j...@psilosoph.de> --- Created attachment 182187 --> https://bugs.documentfoundation.org/attachment.cgi?id=182187&action=edit Clarification and demo of a workaround (In reply to Regina Henschel from comment #29) > An ODF extension would be needed. The labels are written in a > <chart:categories> element and that is a child of the <chart:axis> element > and not of a <chart:series> element. The <chart:series> element has only the > <chart:domain> child element for the x-values and the > <chart:values-cell-range-address> child element for the y-values. But ( I only refer to X-Y-Scatter, because IO very rarely use different types.): 1. The data source for the labels is described as "Data labels" in the dialog (UI), and can be chosen per series. 2. Trying to assign a different labels range for a different series is neither blocked nor provoking an alert. However, the new range is applied to all the series witzhout further notice. == This is clearly misleading the user, and insofar a bug. === 3. The dialog also offers (by default) to use the values as labels. This may be rarly sensible, but seems to tell me that functionally the ODF representation of the cahjrt and the UI as well as the API don't talk the same language. === A different kind of bug? === 4. On the other hand the actual implementation may have a way to use "hidden series" as sources for er4xplicit labels NOT being categories withot violating the needs concerning the saving to an ODF. Do YOU know? I will attach a not quite miniomal example wherte labels from extra ranges are implemented by user code. It may not help concerning prpobable conflicts with ODF stanbdards, but it surely can show what I would expect a reasonable solution to be capable of. Generally a solution saving info about source-ranges for labels per series wolud be clear, useful and allowe for simplification of the 'Format Data Labels' dialog (which isn't exactly about formattiong). -- You are receiving this mail because: You are the assignee for the bug.
