[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#46827: Broken initial size of GTK3 frame
From: |
Eli Zaretskii |
Subject: |
bug#46827: Broken initial size of GTK3 frame |
Date: |
Mon, 01 Mar 2021 16:07:50 +0200 |
> From: martin rudalics <rudalics@gmx.at>
> Date: Mon, 1 Mar 2021 09:31:20 +0100
>
> It turns out that the "something else" is just that
>
> /* Querying further backends can be very slow, so we only do
> it if the user has explicitly requested it (Bug#43177). */
> if (query_all_font_backends == false)
> break;
>
> The attached patch reverting 58430f29968a5661caff630d20dbbe7c864fe08d
> and removing the entity above fixes the bug on master.
Thanks, but removing the zero_vector entity is a non-starter. We paid
dearly for that change, so I don't want to get that problem back
again.
The other change is also quite important.
We need to find a better way of fixing this problem.
- bug#46827: Broken initial size of GTK3 frame, (continued)
- bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/02
- bug#46827: Broken initial size of GTK3 frame, Eli Zaretskii, 2021/03/02
- bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/03
- bug#46827: Broken initial size of GTK3 frame, Eli Zaretskii, 2021/03/03
- bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/03
- bug#46827: Broken initial size of GTK3 frame, Eli Zaretskii, 2021/03/06
- bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/06
- bug#46827: Broken initial size of GTK3 frame, Stephen Berman, 2021/03/02
- bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/02
- bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/01
bug#46827: Broken initial size of GTK3 frame,
Eli Zaretskii <=
bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/01