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 80725 - Expr entry Widget does not accept range sel.
Expr entry Widget does not accept range sel.
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI Expression Entry Widget
git master
Other Linux
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
: 359438 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-05-03 18:27 UTC by Andreas J. Guelzow
Modified: 2010-07-14 06:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andreas J. Guelzow 2002-05-03 18:27:53 UTC
new gnumeric
in A1 enter   =sum(34)
click between 3 and 4
try to select a range.

THe same probelm occurs also in dialogs with expr entry widgets. Typing
there 34 into an entry locks the entry for range selection.
Comment 1 Jody Goldberg 2002-10-07 04:17:13 UTC
Hmm, this does not seem like a bug.
what are you expecting to happen ?
Comment 2 Andreas J. Guelzow 2002-10-07 12:51:26 UTC
Well, if my cursor sits at the | in =sum(3|4) and I select A2:A5 I
would have expected to obtain =sum(A2:A5). As a user I probably
wouldn't try to select a range on the sheet unless I expect that range
to be entered in the entry box. 

While it may be arguable whether I am justified to expect that
behaviour, I would think that if I select 34 in =sum(34) then range
selection should definitely work. 
Comment 3 Jody Goldberg 2004-08-29 03:54:17 UTC
I'm still worried about handling things like
=foo("abc12|3")
Comment 4 Jody Goldberg 2008-07-14 10:58:32 UTC
re-examining this in light of my work on rangesel.
I'm makeing two major changes in the way things are handled
1) Moving the parsing of intersheet, and interbook references down into the reference parsers, out of the grammar.
2) exposing the lexer from the the parser for use by the rangesel mechanism.

That will give us the power to recognize that "3|4" is a string that should be replaced in it's entirety.
Comment 5 Andreas J. Guelzow 2009-11-30 05:45:41 UTC
*** Bug 359438 has been marked as a duplicate of this bug. ***
Comment 6 Andreas J. Guelzow 2010-07-14 03:09:00 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 7 Andreas J. Guelzow 2010-07-14 03:19:39 UTC
apparently git ate my changes
Comment 8 Andreas J. Guelzow 2010-07-14 06:06:47 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.