On 11/09/2007 02:04 PM, NoOp wrote:
> On 11/09/2007 12:41 PM, Joe Conner wrote:
>> I had something similar happen.  See  
>> http://www.openoffice.org/issues/show_bug.cgi?id=82676
>> for the issue that I filed, and the goat-rope that followed.
>> 
>> 
> 
> Well... one can only wonder if you *really, really* are running Windows
> XP. Are you 100% sure :-)
> 
> Observation: I tried your 'Giving Trend Study' on (U)OOo 2.3[1], OOo
> 2.3, and StarOffice 8/8 - all on linux, and can verify that the data
> points do disappear when when the chart is double-clicked for editing.
> 
> However, I noticed when clicking cell A1 and checking styles, there is a
> style called "Excel_Builtin_Currency" linked with the "Default" style.
> For the heck of it I selected all on the spreadsheet (click upper left)
> and changed the style to "Default". Once I did this I could then edit
> the chart properly.
> 
> I then deleted the "Excel_Builtin_Currency" from the spreadsheet & save
> using a different name. Reopened check again - works.
> 
> So my "guess" is that the problem has something to do with the
> "Excel_Builtin_Currency" style. Try deleting the style in your WinXP
> version (are you *sure* you're running WinXP :-), and see if you get the
> same results.
> 
> [1] (U)OOo = Ubuntu OOo.
> 
> Gary
> 

Now, here's something interesting; removing the "Excel_Builtin_Currency"
style from "Graph Bug.ods" doesn't work. Meaning that the datapoints are
still lost when the graph is double-clicked. I'm unsure what the
difference might be, but removing "Excel_Builtin_Currency" on "Giving
Trend Study 2007.ods" fixes the problem in that spreadsheet and I can
repeat on all of the above OOo types *and* WinXPPro OOo.

Another interesting bit; if I save "Graph Bug.ods" as an xls file, none
of the datapoints are preserved when I reopen the file in OOo. However,
when I save "Giving Trend Study 2007.ods" as an xls file, all of the
datapoints are preserved *and* I can edit the graph even with the
"Excel_Builtin_Currency" style left in the spreadsheet.

So now you have a reproduceable situation that a developer should be
able to figure out fairly quick. You might want to update the bug
accordingly, or if you'd like I'll be happy to add my findings there; up
to you.

Gary

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to