Re: [g-a-devel] Label both before and after an editable?

[Samuel Thibault <samuel thibault ens-lyon org>]

Hello,

So, any opinion on this?  How to make this move forward?  There are such
examples in LibreOffice which make the screen reading really odd, we'd
really want to fix it.

Samuel

Samuel Thibault, le lun. 05 mars 2018 15:48:09 +0100, a ecrit:
> Hello,
>
> I'm also getting the case of a label after the widget only: in a preview
> dialog box, there is only an editable containing "1" and a label
> containing "/2" after that.
>
> I tried to use flows-to/from, it didn't work, and it looks distorted to
> me anyway.
>
> Perhaps we should introduce RELATION_LABEL_AFTER_FOR,
> RELATION_LABELLED_AFTER_BY?
>
> Samuel
>
> Samuel Thibault, on mar. 27 févr. 2018 18:34:08 +0100, wrote:
> > We have seen in various places that an editable field has a label both
> > before and after. For instance, in LibreOffice's Tools->Options dialog,
> > in the LibreOffice->General section, there is
> >
> > "Interpret as years between 1930 and 2029"
> >
> > where "Interpret as years between" is a label, "1930" is an editable,
> > and "and 2029" is another label.  Currently in the .ui file the first
> > label is set as mnemonic_widget for the editable, so that orca displays
> > "Interpret as years between 1930", but this is not enough to understand
> > what that is without the last label :)
> >
> > Is there a way to let orca know that there are actually two labels,
> > one before and one after the editable?  I thought perhaps relation
> > flows-to/from in addition to the mnemonic_widget or label-for, but I'm
> > really not sure.
> >
> > The same situation happens in various places where the second label
> > provides the unit, or more precise specifications (e.g. "Distance 0cm
> > between pages" where "0cm" is editable)

-- 
Samuel
<macavity> bash: ls: Computer bought the farm
<macavity> THAT frightens ppl! :P
<macavity> id rather see: "bash: ls: Initialization of googol(AWAX)
        disengaged in HYPER32/64 mode due to faulty page request at
        AX:12A34F84B"
<macavity> at least that would give me the feeling that the
        *programmers* knows what is going on :P
(lovely Hurd...)