[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: long-standing GTK bug
From: |
Madhu |
Subject: |
Re: long-standing GTK bug |
Date: |
Thu, 03 Mar 2022 21:01:50 +0530 |
* Po Lu <87fsnzrxtq.fsf@yahoo.com> :
Wrote on Thu, 03 Mar 2022 21:05:05 +0800:
> Madhu <enometh@meer.net> writes:
>> i think the mainloop crashed elsewhere when some other gsource fired
>> - i don't have my test code and have to do it again maybe later this
>> week.
>
> I look forward to your results.
I see I had misunderstood what you had said about multiple displays. The
simple.c code assumes there is only one display at a time. I'll try to
handle multiple displays and one display dying first.
- Re: long-standing GTK bug, Adam Sjøgren, 2022/03/01
- Re: long-standing GTK bug, Po Lu, 2022/03/02
- Re: long-standing GTK bug, Madhu, 2022/03/03
- Re: long-standing GTK bug, Po Lu, 2022/03/03
- Re: long-standing GTK bug, Madhu, 2022/03/03
- Re: long-standing GTK bug, Po Lu, 2022/03/03
- Re: long-standing GTK bug, Madhu, 2022/03/03
- Re: long-standing GTK bug, Po Lu, 2022/03/03
- Re: long-standing GTK bug,
Madhu <=
- Re: long-standing GTK bug, Lars Ingebrigtsen, 2022/03/03
- Re: long-standing GTK bug, Po Lu, 2022/03/03
- Re: long-standing GTK bug, Lars Ingebrigtsen, 2022/03/04