[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row (see comment 7)

[bugzilla-daemon]

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

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row (see comment 7)

[bugzilla-daemon]

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

Eike Rathke  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Eike Rathke  ---
This has been implemented for 5.1, see
https://wiki.documentfoundation.org/ReleaseNotes/5.1#Sticky_end_column.2Frow_anchors

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row (see comment 7)

[bugzilla-daemon]

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

Beluga  changed:

   What|Removed |Added

 Status|REOPENED|NEW
 CC||todven...@suomi24.fi
Summary|Inserting a row or column   |Inserting a row or column
   |corrupts the Contents   |corrupts the Contents
   |property of a NamedRange|property of a NamedRange
   |for an entire column or |for an entire column or
   |entire row  |entire row (see comment 7)

--- Comment #8 from Beluga  ---
Bug does not meet the criteria for Status 'REOPENED'
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/REOPENED#Criteria
Status -> NEW

Not sure, if it would be better to create a new report.. adjust summary to
something better, if you can.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row (see comment 7)

[bugzilla-daemon]

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

--- Comment #9 from Alex  ---
As the submitter of the original bug report, I consider the flaw I reported to
have been fixed with version 5, and will leave the Summary as is.  Marcelo's
observation in Comment 6 is an elaboration of the flaw I reported, and deserves
consideration.  I will leave it up to him how he wants to proceed with the
issue he described and upon which I expanded in Comment 7, primarily because I
don't think the underlying changes needed to address that situation will be
easy to implement.  My view is that if current versions of Excel can support a
feature, then it should be the goal of LibreOffice to do the same.  There are
presently far too many situations where LibreOffice lags Excel's capabilities,
and I believe these deficiencies should be the first to be addressed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

--- Comment #6 from Marcelo  ---
I had the same problem and I could say this bug still exists on 5.0.0.5 and
recent 5.0.2 versions. The problem resides if range starts from ROW 3 for
example and a reference $A$3:$A$1048576 cannot (should not) converted to $A:$A.
In this case, inserting a new ROW breaks the named reference to $A$3:$A$#REF!.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

--- Comment #7 from Alex  ---
I think Marcelo's observation is slightly different, although no less valid. 
What I reported had to do with the case of an entire row or column, and the
implied need (which had already been recognized by the developers of Calc and
addressed with version 5) for being able to specify it without reference to the
first or last column of a row, or the first or last row of a column.  Marcelo's
situation, as I understand it, is different in that he wants less than an
entire row or column, but wants the upper end of that partial row or column to
be whatever the sheet's last possible range is.  One could "fix" the case he
gives by having Calc automatically check the last row or column of a named
range whenever it was being expanded, and not allow the upper range to exceed
the sheet's maximum.  However, if -- instead of inserting new rows or columns
-- he deleted rows or columns from such a range, Calc would have no way of
knowing to keep the named range at its max value, and so would reduce the upper
value by as many rows or columns as were removed.  So, it seems to me that the
user would have to have some way of indicating, when a named range was being
created, that the range extended to the last possible row/column, and was to be
maintained as such despite subsequent insertion or removal of columns/rows. 
Whereas an entire column can now (as of version 5) be specified as "$A:$A",
what Marcelo seems to be implying is that something equivalent to "$A3:$A"
needs to be recognized as a column beginning at row 3 and extending all the way
to the last possible row of the sheet, and retained as such despite supsequent
insertions or deletions of interim rows.  I don't know if present versions of
Excel can handle this, but the old version 5.0 of Excel that I continue to use
(even under Wine and Linux) can't handle it.  I will add that expecting a user
to specify the last possible row or column by its actual value is unreasonable
because (1) who can remember such values, and (2) these limits could change
with future versions.  So, to properly address the situation Marcelo describes
requires a new accepted syntax for so indicating an upper column/row limit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

raal  changed:

   What|Removed |Added

 CC||chriss...@gmail.com

--- Comment #5 from raal  ---
*** Bug 93812 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

Cor Nouws c...@nouenoff.nl changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #4 from Cor Nouws c...@nouenoff.nl ---
Thanks for confirming.
Since 4.4.x is not end of life, it's good to keep this bug open.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

Alex alex6...@postedmail.net changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Alex alex6...@postedmail.net ---
I can confirm that the reported bug is still in 4.4.5.1, but am I delighted to
report that it has been fixed in 5.0.0.5!  I extend my appreciation to those
who have brought this aspect of NamedRanging in Calc up to where Excel 5.0 was
20 years ago.  I look forward to the time when NamedRanges local to Sheet1, for
example, can be referenced in a formula on Sheet2 with a syntax like
=Sheet1.LocalName as Excel has supported for 2 decades.

What I really appreciate about the way this bug has been fixed is that
NamedRanges which are entire rows or entire columns are now so indicated by
Excel-like nomenclature (i.e., C:C or 1:1, rather than C1:C1027593848 or
A1:AMJ1).

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

--- Comment #3 from Alex alex6...@postedmail.net ---
The first line of the above should have said the bug remains in 4.4.5.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 93264] Inserting a row or column corrupts the Contents property of a NamedRange for an entire column or entire row

[bugzilla-daemon]

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

Cor Nouws c...@nouenoff.nl changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||c...@nouenoff.nl
 Ever confirmed|0   |1

--- Comment #1 from Cor Nouws c...@nouenoff.nl ---
Hi Alex,

Thanks for your report.
4.4.4.3 has subsequent releases with 4.4.5.1 and 4.4.5.2.

Can you please check if the problem exists in 4.4.5.2 too?
If so, checking in 5.0.0.5 would be appreciated and a test file.

If not, you may close this issue as WorksForMe (Fixed is used when we know the
commit that solved the problem.)

thanks again,
ciao,
Cor

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs