On 07/03/12 at 06:36pm, Bjartur Thorlacius wrote:
> On Tue, Jul 3, 2012 at 5:56 PM, Manolo Martínez
> <[email protected]> wrote:
> > None of that works: dwm keys are, as I say, unresponsive in fceux
> > fullscreen. When trying sleep + xprop, xprop complains that it can't
> > "grab the mouse".
> >
> Can you verify that the rectangle is in fact not a new top-level
> window but an in-window artifact of SDL by logging window mapping
> requests in your X11 server.
>
> Something like the following Pseudo-C snippet, or preferably a gdb
> trace, should do the job.
> | case MapRequest:
> [..]
> | fprintf(stderr, "XID:\t%i", Req->Window);
> | break;
>
Is the attached patch what you meant? (Sorry, my C is very basic).
If it is, when I open new windows they do leave a XID at my
/tmp/errores.txt file but, interestingly, fceux does not. Not even the
tiny floating window, let alone the fullscreen version.
It's entirely possible that I have misinterpreted your instructions, though.
Let me know if that's the case.
Cheers,
Manolo
diff -r 2139e30c2169 dwm.c
--- a/dwm.c Sun Jun 24 09:36:47 2012 -0400
+++ b/dwm.c Tue Jul 03 15:22:25 2012 -0400
@@ -1182,7 +1182,7 @@
if(ev->request == MappingKeyboard)
grabkeys();
}
-
+FILE *errores;
void
maprequest(XEvent *e) {
static XWindowAttributes wa;
@@ -1193,6 +1193,9 @@
if(wa.override_redirect)
return;
if(!wintoclient(ev->window))
+ errores = fopen("/tmp/errores.txt", "a+");
+ fprintf(errores, "XID;\t%lu\n", ev->window);
+ fclose(errores);
manage(ev->window, &wa);
}
