FWIW, the wrapping of the last digit only occurs in OOo1.0.2 on RH9, 
also.

This was found on a different machine.

I guess it wouldn't sound so confusing if I rewrote the last entry as:
FWIW, the wrapping of only the last digit also occurs in OOo1.0.2 on 
RH9.

Doug

Hi Doug,

it's the wrong component. I changed it.

Frank

duplicate

*** This issue has been marked as a duplicate of 11561 ***

closed

First, issue 11561 was closed as INVALID, CND.  Therefore it wasn't 
resolved.  Also, I fail to see how it is a duplicate of this problem.

Second, I have produced the symptoms reported on two completely 
different sets of hardware in two different versions of OOo.  On top 
of which, the copy of 1.0.2 came with RH9 and 1.1RC3 was from OOo 
mirrors.

The symptoms I reported are real.  They are easy to replicate.  What 
more information can I provide to help you isolate the source of the 
problem?

Doug

Hi, Doug.  I'm just another user, but I tried to duplicate your
problem and couldn't, but the reason is likely that I am using 1.1RC3
and 1.0.3.1.  1.0.2 made far fewer changes than 1.0.3.1 and a lot of
such things were fixed there.  1.1RC3 is very stable and the full 1.1
is due out soon.

Remember these are bug reports to fix problems in an ongoing
development process, not issue patches for older versions.  I believe
by the time they get to 2.0, we'll have patch capabilities (if I read
them right), but right now, I think the fix would be to upgrade the
ancient 1.0.2 to something more "bug-free" and "enhancement rich" such
as 1.0.3.1 (stable) or 1.1RC3 (almost as stable but a vast
improvement).  Or, of course, you can wait for the 1.1 which is due in
a couple of weeks.

But if your bug no longer exists on a current version of a free
software pachage, it's going to be marked as "Worksforme" or "invalid"
simply because, having already been fixed, there is nothing to fix.

Robert,

1.  Read the bug report.  What does it say under version at the top of 
this page?  While I have gone through Ooo1.1rc3 in both Win98 and RH9 
for this update, please note that all of the following has also been 
duplicated in Win98SE/OOo1.1rc2 as of this writing. All of this work 
has been performed on an AthlonXP 2100 system with 512 MB RAM.

2.  My earlier followup was to show that the identical symptoms were 
exhibited in a prior version and under another OS.  The intent was to 
provide additional information to be able to localize a possible 
source of the problem.  It was also to demonstrate that if a "fix" had 
been accomplished, it had been neutralized in some later release.

3.  Perhaps the following recipe will allow you to duplicate:
  a.  Create a table with dates in Column A for half a dozen rows, or 
so.
  b.  Populate four or five more columns with numeric values  for the 
same number of rows.
  c.  Create a horizontal bar chart from these values.

4.  I have now gone through all the date formats.

Note that there are two formats shown as 12/31/99, but if you look at 
the format codes one is M/D/YY and the other is MM/DD/YY

Use the first 12/31/99 date format and a current date in August, which 
becomes a one digit month, and the label displays as: 
8/21/03

Using a two digit month  _or_  the MM/DD/YY format and the label wraps 
as:
12/21/0
3
   or
08/21/0
3

Finally, using the selection 12/31/1999, which formats as MM/DD/YYYY, 
yields:

08/21/2
003

All of the other date formats wrap logically.

I haven't the experience with the OOo source to go looking for the 
cause of this behavior nor do I claim to be a programmer.  But my 
resumè documenting specifying and testing complex, computer-based data 
and control systems for aerospace applications is longer than your 
arm.  In other words, trust me, there is an inappropriate behavior.  
The best I can contribute right now is to document its existence and 
how to reproduce it.

Doug  

BH-> That should be fixed in the new Chart.

Hello Björn, some date formats make problems by causing that mentioned
wrapping. Please approve accordingly. Thank you.

Hi Doug,

I am still not quite sure, what exactly the problem is.  First of all,
try unchecking 'Break' (on the Options Tab-Page of the x-Axis). This
prevents the labels from starting new lines, however they may overlap
then (if there is really enough space they shoudln't).  If they do,
you can uncheck 'Overlap', then some labels are hidden.  You can also
try 'Stagger odd/even' for getting more space per label.

You said, resizing wouldn't help.  What happens, if you only change
the width (this doesn't rescale the text)? This should result in a change.

The problem when you have 'Break' checked is that the available width
before text is broken has to be less than the total available space,
otherwise the text would look glued together even with breaks.

Does the changing of the 'Break' flag help you or do you still see an
issue?

please verify, if this also works for you. If so, please close this issue.

According to Doug's personal mail:
> I would reply on IZ, but my login no longer works and I don't
> feel compelled to re-register.  I thought I had replied
> already, but obviously not.
>
> Unsetting the Break Flag corrects the behavior.

it seems ok for me to close this bug.

how can I close this ...

->Thomas: Are you able to close this bug? Thanks.

Yes, i will do it for you.

closed