I just tried to remove the cursor from my GTK+-DirectFB "set-top" application by commenting out
DisplayLayer->EnableCursor (DisplayLayer, 1);
in gdkmain-directfb.c. I know this is a hack, but a) it should be
possible to do this sort of thing and b) I was testing the concept
before going any further with it.
Anyway, I noticed that my keypress/keyrelease events no longer get
sent to windows on the layer with the cursor disabled. What is the
theory of this? Why should (a) window(s) on a layer without a cursor
not get keyboard (or IR!) events?
I can go along with suppressing window movement events, but there
really is no relation to not having a cursor and not wanting/receiving
keyboard events.
Thots? Can we get rid of this restriction?
--- src/core/windows.c.old 2002-11-18 13:50:58.000000000 -0500
+++ src/core/windows.c 2002-11-18 13:51:02.000000000 -0500
@@ -1568,8 +1568,6 @@
break;
case DIET_BUTTONPRESS:
case DIET_BUTTONRELEASE:
- if (!stack->cursor.enabled)
- break;
stack_lock( stack );
b.
--
Brian J. Murrell
msg01082/pgp00000.pgp
Description: PGP signature
