[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: long-standing GTK bug
From: |
Po Lu |
Subject: |
Re: long-standing GTK bug |
Date: |
Thu, 03 Mar 2022 15:21:57 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Madhu <enometh@meer.net> writes:
> I tried to do a proof of concept using XSetIOErrorExitHandler to prove
> it was possible to kill the display and still have a gtk app running.
>
> https://gitlab.gnome.org/enometh/simple4/-/raw/master/simple.c
>
> which seemed to work. the code is a bit crufty as it includes the
> longjmp path , and i have to reread it to understand it and my headaches
> are interfering with thinking. When i checked there was some other snag
> in moving this to emacs
Display *dpy = gdk_x11_display_get_xdisplay(gdpy);
XSetIOErrorExitHandler (dpy, x_io_error_exit_handler, &done);
=> window = gtk_window_new ();
gtk_window_set_title (GTK_WINDOW (window), "hello world");
Judging by the absence of arguments to `gtk_window_new', this code is
for GTK 4, correct?
The X and GTK configuration will never work with GTK 4 due to other
fundamental changes in the toolkit, and PGTK will not be able to access
X-specific APIs.
Thanks.
- 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 <=
- 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, 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