Bug 95847 - Error with log scale starting at 0: says it "can't use a negative number"
Summary: Error with log scale starting at 0: says it "can't use a negative number"
Status: RESOLVED DUPLICATE of bug 82584
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: x86 (IA32) All
: low trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Error-Messages
  Show dependency treegraph
 
Reported: 2015-11-16 09:41 UTC by Carl Ponder
Modified: 2023-07-10 15:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Ponder 2015-11-16 09:41:56 UTC
I'm using Calc to draw a semilog plot, i.e. the horizontal axis is linear but the vertical axis is logarithmic.
I'm reporting the y axis as units of time, i.e. hh:mm:ss.
I had (incorrectly) used 0 as the minimal value, which doesn't' work for log.
But the message said "Can't take the log of a negative number", which I incorrectly assumed to mean it couldn't deal with the time units.
The message should have said it couldn't take the log of zero.
Comment 1 Buovjaga 2015-11-16 17:53:25 UTC
For me it says:
"The logarithmic scale requires positive numbers. Check your input."

Are you suggesting that the message should say:
"The logarithmic scale requires positive numbers, while you inputted <value>."

Or something to that effect.

Win 7 Pro 64-bit, Version: 5.0.3.2 (x64)
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale: fi-FI (fi_FI)

Version: 5.1.0.0.alpha1+
Build ID: b216cc1b8096eb60c27f67e8c27b7cd756c75e38
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-12_00:06:20
Locale: fi-FI (fi_FI)
Comment 2 QA Administrators 2017-01-03 19:35:20 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2021-03-19 04:41:49 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-03-20 03:27:01 UTC Comment hidden (obsolete)
Comment 5 Regina Henschel 2023-07-10 15:31:36 UTC
Let's track the problem in bug 82584.

*** This bug has been marked as a duplicate of bug 82584 ***