On 03 Jun 2001 05:21:36 +0200, Tomas Ogren wrote: > > There's still (cvs as of now) problems with focus in Nautilus.. I've > been busy+++ lately, but I will have spare time to spend now.. It > doesn't get any focus..
I though Dominik fixed this... Did not the Nautilus author plan to fix this in Nautilus too without using rare ICCCM features? > There is also a problem when an app sets it's (GNOME) WM layer before > the window is shown. It then sets a property on the window which level > it's supposed to be on, but it doesn't get read by fvwm it seems... > I see the code in gnome.c and style.c to read it, but I don't know which > order stuff is happening/supposed to happen, so it's a bit hard... > > Attached is a test program written in gtk/xlib... > create some windows on layer 4 and then start the program.. one of the > windows is supposed to land on layer 3 (below the others).. then you can > raise/lower it with the up/down buttons.. > > If given any argument to the program, it will show (map) the window > before trying to set the layer which makes it end up on the correct > layer directly (almost.. you can see it starting infront of the windows, > then jumping back) 1) There is a typo in the program, so it can't be compiled without a fix, the variable "level" should be replaced with "layer" globally. 2) To compile it: gcc -o winhints `gtk-config --cflags --libs` winhints.c 3) I can't reproduce any problem with this program, it works just well with or without arguments. Of course it is not consistent because it first requests to place itself to "layer-1" and then to "layer". But if you patch the program to replace "layer-1" with "layer" it will become consistent. A note, it is intended that a window is lowered in FVWM when it changes a layer, say from 5 to 4, and raised - when changes a layer from 3 to 4. % gtk-config --version 1.2.10 Am I missing something? Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
