Bug 208966 - [x86_64] regression in openoffice writer, table references broken in expressions
Summary: [x86_64] regression in openoffice writer, table references broken in expressions
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-02 19:39 UTC by Henrik Nordstrom
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 2.0.4-5.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-11 10:55:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenOffice.org 70061 0 None None None Never

Description Henrik Nordstrom 2006-10-02 19:39:30 UTC
Description of problem:

References to able cells no longer works in OpenOffice writer formulas. Worked
in FC5.

Version-Release number of selected component (if applicable):

openoffice.org-writer-2.0.4-5.1

How reproducible:

Always.

Steps to Reproduce:
1. Insert a table (at least 2 cells)
2. Enter the digit 1 in the first cell
3. Press F2 in another cell and enter 5 + and click on the first cell
  
Actual results:

** Invalid Expression **

and in the the expression the reference to <A1> has been replaced by <?>

Expected results:

Automatic calculation of the contents of the first cell + 5.

Additional info:

Works fine in Fedora Core 5 openoffice.org-writer-2.0.2-5.19.2

Comment 1 Caolan McNamara 2006-10-03 08:10:40 UTC
On i386 I e.g. get =5+<A1> and hitting return calculates as expected, I can't
reproduce this. Are you on x86_64, or i386 or ppc ?

Comment 2 Caolan McNamara 2006-10-03 09:05:17 UTC
I can reproduce this under x86_64, and have a fix. Checked in, will be in next
respin

Comment 3 Henrik Nordstrom 2006-10-03 09:21:32 UTC
x86_64 as indicated in the hardware field.

Comment 4 Caolan McNamara 2006-10-03 09:43:46 UTC
yeah, but I set that field :-)


Note You need to log in before you can comment on or make changes to this bug.