https://bugs.documentfoundation.org/show_bug.cgi?id=161748

--- Comment #10 from ady <adylo811...@gmail.com> ---
(In reply to Per99 from comment #9)
> (In reply to ady from comment #8)
> > In LO 24.2, the MS Windows setting that allows (or not) animations impacts
> > the behavior in Calc for "marching ants". This was not the case in LO 7.6.
> > 
> > The OS setting enables/disables _all_ animations, and I agree, that is not
> > what some users need; some animations are not strictly necessary (making the
> > OS slower) whereas others are really helpful for accessibility.
> > 
> > Basically, you are requesting that the "marching ants" behavior in LO should
> > depend only on LO's settings, and not to depend on OS's settings.
> > 
> > FWIW, +1 from me.
> > 
> > CC'ing Michael.
> 
> Yes, either
> a) > Basically, you are requesting that the "marching ants" behavior in LO
> should depend only on LO's settings, and not to depend on OS's settings.
> 
> or
> b) Enable the user to turn on "marching ants" animation by either setting

The settings currently available in LO/Calc should give enough alternative
customization (especially for accessibility reasons), and should prevail,
IMNSHO.

FWIW, I disagree with your "b" (IIUC, which I'm not sure I do). One user might
want the animated ants in Calc while the OS's setting for animation is OFF, and
OTOH some other user might want the exact opposite case (for whichever reason).
So, the behavior in Calc should rather be set by Calc settings, and not imposed
(on any direction) by the OS's settings. At most, the OS's settings (as the
user sets them) could be taken as the default for the program's behavior in
that system, but then LO's settings should prevail (especially when they are
modified/customized by the user). This is my personal opinion, not just in the
case of animations.


@Per99,

As a side note, please try to be more concise, please avoid repeating what was
already said, and please do not quote entire comments unnecessarily. TIA.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to