After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 706671 - Internal links are stored as strings rather than expressions
Internal links are stored as strings rather than expressions
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI Expression Entry Widget
git master
Other All
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-08-23 15:23 UTC by Michael Uplawski
Modified: 2017-03-06 01:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
an attempt to modify an existing internal link. (77.28 KB, image/png)
2013-08-23 15:23 UTC, Michael Uplawski
Details
Evolving database of my vegetable-seeds. (11.86 KB, application/x-gnumeric)
2013-08-23 20:16 UTC, Michael Uplawski
Details

Description Michael Uplawski 2013-08-23 15:23:14 UTC
Created attachment 252879 [details]
an attempt to modify an existing internal link.

Gnumeric 1.12.4
Ubuntu Linux 13.04
Fluxbox/Rox

In a worksheet of several tables, I decided to split-up one table on several dedicated tables. As some links point at the original table, I have to adapt them in the source-tables.

Doing so by pointing with the mouse on the new target range, produces invalid range references, like TableName!A4:A5!A5:A6. See Screen-shot. In the screen-shot, please ignore all those bizarre tooltips. They are subject to another bug-report (https://bugzilla.gnome.org/show_bug.cgi?id=706659).

As a consequence, all links must anyway be modified manually.

Cheerio.
Comment 1 Andreas J. Guelzow 2013-08-23 19:44:58 UTC
I cannot replicate this. Would you please describe step by step what you are doing?
Comment 2 Michael Uplawski 2013-08-23 20:16:14 UTC
Created attachment 252948 [details]
Evolving database of my vegetable-seeds.

This version of the file contains the tables 'semer', 'repiquer' and 'recolter' which replaced one table 'saisons'.
Comment 3 Michael Uplawski 2013-08-23 20:17:26 UTC
Okay, I see there is a critical point in the procedure. The phenomenon can be observed only, when you rename (or remove) the table that has originally been the target of workbook-internal links.

What I did was the following:
1. rename a table «saisons» to «semer»
   This enders all links pointing to ranges in 'saisons' invalid.
2. create two new tables «repiquer» and «récolter»
3. went to another table, where I modified all existing links to 'saisons'. 
   Middle-click on a cell, containing a link, 
   select "internal link" (sorry, my Gnumeric speaks German, I do not know what 
   it proposes in the english locale),
   clicking the button which allows to point at the target range.

Voilà. I mean, there! 

The file is the one, that you know from the other bug but I add as an attachment to this message the current version with the new tables.
Comment 4 Andreas J. Guelzow 2013-08-23 20:45:30 UTC
Okay, I see. So th eproblem isn't really the behaviour of the expression entry. YOU are starting with an invalid expression and so the entry selects a valid portion of it.

The real issue is that as the sheet is renamed the internal links are not correctly adjusted. There should be no need for you to adjust  hte link addresses to the new sheet name.
Comment 5 Michael Uplawski 2013-08-23 20:53:59 UTC
(In reply to comment #4)
> There should be no need for you to adjust  hte link
> addresses to the new sheet name.

Thank you for this opinion... or do you think it was meant that way in the beginning.. ? ;-> never mind.
Comment 6 Andreas J. Guelzow 2013-08-23 22:14:01 UTC
I really can't imagine that anybody intentionally wanted to keep the name of the internal link address fixed. We don't do that anywhere else in Gnumeric. So I think that is just a bug that wasn't reported (probably because few people use internal links.)
Comment 7 Morten Welinder 2017-03-03 20:50:22 UTC
I just hit that while creating test cases.
Comment 8 Morten Welinder 2017-03-06 01:29:40 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.