| commit | 6d9bcfabc727e97536364f6f0bda12fc85876ac2 | |
| author | Caolán McNamara <caolanm@redhat.com> | |
| Wed, 18 May 2022 15:33:57 +0000 (18 16:33 +0100) | ||
| committer | Michael Stahl <michael.stahl@allotropia.de> | |
| Mon, 20 Jun 2022 09:02:25 +0000 (20 11:02 +0200) | ||
| tree | 76ce1e79b9e5f078387007878d8f5acfb0b8a5d3 | treesnapshot (tar.gz zip) |
| parent | b95071969d95cbf3d56b53286ccefd4c43033fc1 | commitdiff |
tdf#141186 ensure child of collapsed expander is not mapped
If the expander is initially collapsed then when mapped all its children
are mapped too.
If they are mapped then the mnemonics of the children are taken into
account on shortcuts and non-visible children in a collapsed expander
can be triggered which is confusing.
If the expander is expanded and collapsed the child is unmapped
and the problem doesn't occur.
So to avoid the problem of an initially collapsed expander, listen to
the map event and if the expander is mapped but collapsed then unmap the
child of the expander.
Change-Id: Ib4c7a704295b338230357c4c4102a3692f8a9707
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134453
Tested-by: Jenkins
Reviewed-by: Michael Stahl <michael.stahl@allotropia.de>
If the expander is initially collapsed then when mapped all its children
are mapped too.
If they are mapped then the mnemonics of the children are taken into
account on shortcuts and non-visible children in a collapsed expander
can be triggered which is confusing.
If the expander is expanded and collapsed the child is unmapped
and the problem doesn't occur.
So to avoid the problem of an initially collapsed expander, listen to
the map event and if the expander is mapped but collapsed then unmap the
child of the expander.
Change-Id: Ib4c7a704295b338230357c4c4102a3692f8a9707
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134453
Tested-by: Jenkins
Reviewed-by: Michael Stahl <michael.stahl@allotropia.de>
| vcl/unx/gtk3/gtkinst.cxx | diffblobblamehistory |