Dear all

I'm not sure this is a right fix but some how in the gtkfb
the unique will create a decorate window as big as screen
and not visible, so when you click on the foo it will call
the grab window and the pointer input channel will be switch
to a invisible layer, so I put a test of the window->opacity
before the switch

--- window.orig 2006-01-06 00:39:21.000000000 +0800
+++ window.c    2006-01-06 00:38:41.000000000 +0800
@@ -492,8 +492,13 @@
                                                UDCI_KEYBOARD,
window->channel );

           case CWMGT_POINTER:
+               if( window->opacity )
                return unique_input_switch_set( context->input_switch,
                                                UDCI_POINTER,
window->channel );
+               else {
+                //printf("Alex say this is not good so don't set!\n");
+                return DFB_OK;
+               }

           case CWMGT_KEY: {
                DFBResult          ret;



Alex Lau wrote:
> I find out the id of the window and the decorator is two different thing
> and when I click on the decorator the decorator window seem to get all
> the input and not able to give it back to the window.
> how should I handle that?
> 
> I put some function in unique/window.c, I'm not sure it is correct.
> e.g. move windows and change opacity
> 
> 
> Thanks
> Alex
> 
> _______________________________________________
> directfb-dev mailing list
> [email protected]
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
> 


_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to