Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hello,

this patch makes our check for existing named ranges in
Insert->Names->Define case insensitive. Our formula compiler is already case
insensitive so we shouldn't be able to create two named ranges with the same
case insensitive name.

Regards,
Markus
From c780ab6059ce88ac694d3007f67ed8fe14113d9d Mon Sep 17 00:00:00 2001
From: Markus Mohrhard <markus.mohrhard@googlemail.com>
Date: Mon, 8 Aug 2011 17:20:20 +0200
Subject: [PATCH] fix for fdo#39915: defining named ranges should be case insensitiv

---
 sc/source/ui/namedlg/namedlg.cxx |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/sc/source/ui/namedlg/namedlg.cxx b/sc/source/ui/namedlg/namedlg.cxx
index 6a6053c..17d2d22 100644
--- a/sc/source/ui/namedlg/namedlg.cxx
+++ b/sc/source/ui/namedlg/namedlg.cxx
@@ -388,7 +388,9 @@ bool ScNameDlg::AddPushed()
                 //    in ein Token-Array uebersetzt werden?)
                 if ( 0 == pNewEntry->GetErrCode() )
                 {
-                    ScRangeData* pData = mpCurRangeName->findByName(aNewEntry);
+                    String aUpper = aNewEntry;
+                    aUpper.ToUpperAscii();
+                    ScRangeData* pData = mpCurRangeName->findByUpperName(aUpper);
                     if (pData)
                     {
                         pNewEntry->SetIndex(pData->GetIndex());
-- 
1.7.3.4


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.