Re: [orca-list] Tables in Oo Writer

[Steve Holmes <steve holmes88 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Well, I did some more testing and things don't seem to be consistent;
that makes it really hard to come up with repeatable outcomes.  Once
this evening, I tried the test calendar I have here that models after
yours and when I positioned my cursor over the column Monday, I did
the insert-r to activate the row as a column header and everything
worked as we should expect for both tabbing around and using the
structural navigation.  Then after that, while still in the same
document, I tried clearing the dynamic row and resetting it from the
first column, Sunday.  But I couldn't get any different behavior.  But
yesterday, I tried from the Sunday column and only could get the two
first column headers to speak.  Now AI went out of Oo Writer and
reopened with my other document which had 3 columns and several rows.
The only way I could get all column headers to speak according to spec
was to press Orca-R on every cell across that row; so in my test
document, I pressed Orca-r on cell A1, B1, and C1.  Then I got the
desired behavior.

I don't know what to think of all this but if I can get the headers to
speak some how, then I'll use it even if it might be a bit clunky.
Again, not sure if the Oo version could affect this problem or not.

On Sun, Jun 21, 2009 at 08:36:15PM -0400, Joanmarie Diggs wrote:
> Hey Steve.
>
> Thanks for testing!
>
> > I have a document with 12 rows and 3 columns.  The top row has titles
> > like "Item", "My Price", and "Your Price".  Now if I go down a few
> > rows and use the new structural nav keys to move left and right, I can
> > only hear the headers spoken for the first two columns; the third
> > column header is never spoken.
>
> Hmmm. That's odd. I just tried it with one of my sample documents and
> things worked as expected. (Isn't that always how it goes?) So let me
> try to describe my document and what I'm doing and see if we can figure
> out the differences.
>
> My document is a sample calendar for one month. There are a couple of
> lines of text above and below the table. The table itself has seven
> columns, one for each day of the week. The first row has "Sun", "Mon",
> "Tue" and so on. In the cells below, are numeric dates.
>
> Here's what I did:
>
> 1. Arrowed into the first row (i.e. the row with the day names which I
> want to be treated as headers).
>
> 2. Pressed Orca + R. Orca announces that the dynamic column headers are
> set for row 1.
>
> 3. I arrowed down into one of the rows with numeric dates and pressed
> Tab and Shift+Tab to move from cell to cell (i.e. not using structural
> navigation). Orca announces the "Sun", "Mon", etc. as appropriate for
> the new column as I move left to right or right to left. If I move up or
> down (i.e. with plain arrow keys) column headers are not announced
> because I have not changed columns.
>
> 4. I pressed Orca + Z to turn on structural navigation. (Orca confirmed
> it had been toggled on.)
>
> 5. I used Orca + Shift + the arrow keys to move around. As I did, Orca
> spoke the days of the week as I moved left or right; not when I moved up
> or down.
>
> 6. Both with tabbing and with structural navigation, I was able to move
> to all of the edges of the table and have the header spoken as
> appropriate.
>
> So.... What is different about your table and/or the commands you're
> using? If we seem to be doing the same thing but getting different
> results, it would be awesome if you could attach the offending table and
> a full debug.out to a new bug. Thanks!
>
> > This seems to happen whether I
> > predefined the dynamic headers with Orca or not.  
>
> This part puzzles me. If you have not predefined the dynamic headers,
> Orca should not be speaking them because it should not have any idea
> where or what they are. <smile> I can confirm that we are not speaking
> headers in my sample case until I have set them. Also, if I later clear
> them (with Orca + R twice quickly), Orca stops announcing the headers.
> If you're always getting headers spoken even though you haven't defined
> them, please file a new bug with the table and debug.out.
>
> > that I'm using.  I thought one might need to somehow define the table
> > row in question to be a header or something.
>
> You do. See my step #2 above.
>
> I hope this helps. Let us know.
> --Joanie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkpBksQACgkQWSjv55S0LfGMBwCdE2LujSBwwAJaUukOfvJltPQX
aEAAoPm8KJo/rGuPTU4QfKHNT3X9CsNk
=SB/1
-----END PGP SIGNATURE-----