[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#46827: Broken initial size of GTK3 frame
From: |
martin rudalics |
Subject: |
bug#46827: Broken initial size of GTK3 frame |
Date: |
Mon, 1 Mar 2021 19:04:07 +0100 |
>> 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.
Agreed to both. I'd just have to understand first how the above can
and do affect redisplay.
martin
- bug#46827: Broken initial size of GTK3 frame, (continued)
- 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, 2021/03/01
- bug#46827: Broken initial size of GTK3 frame,
martin rudalics <=
bug#46827: Broken initial size of GTK3 frame, martin rudalics, 2021/03/01