David Maciejak <[email protected]> escribió:
Hi, I also stumbled upon the same issue (I put the old email in reference below) and dug into it these last days. Rodolfo, as you were the original reporter. Could you please check the patch enclosed ? thanks! david
Hi David, you made my day :-) Patch is perfect. Thanks a lot, Rodolfo.
------------------------------------------------------------------------------------ From e1e12067794c4e53064e59edc3de7af196179369 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?"Rodolfo=20Garc=C3=ADa=20Pe=C3=B1as=20(kix)"?= <[email protected]> Date: Sat, 23 Jun 2012 15:21:24 +0200 Subject: [PATCH] Test environment Hi, we have a bug with stacking. If you check your logfile (~/.xsessions-errors) or the console y you are not using a visual login program (xdm, kdm, gdm,...), you will find something like: wmaker(catchXError(startup.c:177)): warning: internal X error: RenderBadPicture (invalid Picture parameter) Request code: 152 Request minor code: 7 Resource ID: 0x6000a4 Error serial: 9269 This output is created when you deminiaturize a window using double-click. Yes, try now! :-) I spent some time on this problem, but I cannot solve it. I saw an interesting thing. When you minimize the window and then deminiaturize with double click you get the problem. But, if you minimize the window and then deminiaturize it with rigth click on the icon, and then click on deminiaturize, then you don't get the error. Ok, I continue checking the problem, and I created a "Testing enviroment patch" (attached). With this patch, I got this output: --win 0x1a12dd0-- 1 2 5 wmaker(catchXError(startup.c:177)): warning: internal X error: RenderBadPicture (invalid Picture parameter) Request code: 152 Request minor code: 7 Resource ID: 0x6000a4 Error serial: 9269 --win 0x1a499b0-- -.win 0x1a12dd0.- 2 5 -.win 0x1a12dd0.- When I deminiaturize the icon using double click, then "if (frame->stacking->under)" is true, but using the miniwindow menu, the flow is different, and it don't exec the stacking line "frame->stacking->under->stacking->above = frame->stacking->above;". The question is easy, why the "frame->stacking->under" exists if I did double click? Finally, if you see the lines above and below the call to wDeiconifyWindow (printf("--win %p--\n" and printf("-.win %p.-\n", the WWindow address is the same using the menu and different using double click. Any help is appreciated. Best Regars, kix.
Rodolfo García Peñas (kix) http://www.kix.es/ -- To unsubscribe, send mail to [email protected].
