Calc: Print range added to "Named Ranges and Expressions" doesn't show up in the print ranges dialogue if row number has more than 6 digits. If it has 6 digits max it shows up.
Steps to Reproduce:
1. Create empty sheet.
2. Sheet--Named Ranges and Expressions--Manage
3. Create a new range covering $A$1:$A$9999999 and define it as a print range by ticking "Print range" under "Range options".
4. Open Format--Print Ranges--Edit and click at the dropdown menu for adding a range.
The range doesn't show up in the list of named print ranges.
The range should show up as a print range, or, if 7 digits row numbers are too much too handle, I'd like an error message when I try to define it so I know.
User Profile Reset: No
Build ID: 1:6.4.6-0ubuntu0.20.04.1
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3;
Locale: sv-SE (sv_SE.UTF-8); UI-Language: en-GB
It's not the number of digits that are relevant. It works with 1048576 rows max, anything over that will not work.
Why do you expect a print range exceeding the maximum number of rows (2^20 = 1048576
) in a calc spreadsheet (neglecting experimental feature "large sheets" in version 7.0 and later) to work? From my perspective this is not a bug, though it is disputable whether there should be a warning about an out-of-boundary named range.
(In reply to Uwe Auer from comment #2)
> Why do you expect a print range exceeding the maximum number of rows (2^20 =
> ) in a calc spreadsheet (neglecting experimental feature "large sheets" in
> version 7.0 and later) to work? From my perspective this is not a bug,
> though it is disputable whether there should be a warning about an
> out-of-boundary named range.
What makes it a bug is that there's no error message. If I do something that the program will ignore or that will make the program unstable, I expect to get noticed as to why this is so. This is the behaviour in other cases: For example if I try to SUM a too large area, maybe by a writing typo etc, I get a #NAME? in the cell to tell me that something is wrong with the range.
The possibility to enter wrong values need to be checked / prohibited in the UI. Rather than an interrupting message box, the input field should show the error by a different control background via set_message_type(weld::EntryMessageType::Error) and disable the confirmatory action ie. the Okay button.