krotsquared.blogg.se

1. TRANSIENT MULTIMON MANAGER DRIVERS
2. TRANSIENT MULTIMON MANAGER DRIVER
3. TRANSIENT MULTIMON MANAGER PATCH

16:40:58,374 map event: changed workspace from None to -1 16:40:45,875 configure event: changed workspace from -1 to 0 16:40:45,872 map event: changed workspace from None to -1 16:40:35,863 configure event: changed workspace from -1 to 0 16:40:35,862 map event: changed workspace from None to -1 16:40:10,536 TrayBacking does not have any pixel data! 16:40:10,535 TrayBacking does not have any pixel data! 16:40:10,527 configure event: changed workspace from -1 to 0 16:40:10,524 map event: changed workspace from 0 to -1 16:40:10,475 configure event: changed workspace from -1 to 0 16:40:10,463 map event: changed workspace from 0 to -1 16:40:10,333 NOT setting window 770 to screen

16:40:10,329 NOT setting window 726 to screen 16:40:10,306 configure event: changed workspace from -1 to 0 16:40:10,302 map event: changed workspace from 0 to -1 16:40:10,299 configure event: changed workspace from -1 to 0 16:40:10,297 map event: changed workspace from 0 to -1 16:40:10,294 configure event: changed workspace from -1 to 0 16:40:10,293 map event: changed workspace from 0 to -1 16:40:10,246 configure event: changed workspace from -1 to 0

16:40:10,245 map event: changed workspace from 0 to -1 16:40:10,200 configure event: changed workspace from -1 to 0 16:40:10,199 map event: changed workspace from 0 to -1 16:40:10,127 NOT setting window 107 to screen 16:40:10,126 NOT setting window 59 to screen 16:40:10,125 NOT setting window 41 to screen 16:40:10,093 NOT setting window 26 to screen 16:40:10,045 NOT setting window 1 to screen 16:34:04,254 NOT setting window 770 to screen 16:34:04,253 NOT setting window 750 to screen 16:34:04,227 NOT setting window 726 to screen 16:34:04,019 NOT setting window 107 to screen 16:34:04,017 NOT setting window 59 to screen 16:34:04,015 NOT setting window 41 to screen 16:34:03,984 NOT setting window 26 to screen 16:34:03,898 NOT setting window 1 to screen

TRANSIENT MULTIMON MANAGER PATCH

Patch completely fixed horizontal menu positioning issue - thank you so very much for it. It sounds to me like the vertical positioning is a separate issue (different ticket), is it also a regression?ĭo you have wiki/FakeXinerama installed? Does it make any difference?ĭoes the patch above help? If so, what does the client output say? Please post the client and server output of 0.12.x with -d workspace. Set to dont-set-screen-or-workspace.patchĪvoids setting the window screen or workspaceįri, 04:33:24 GMT - Antoine Martin: owner changed Vertical positioning is incorrect on middle monitor where I have KDE task bar (on top): when I drag-n-drop URL to bookmark bar in Iceweasel I have to position mouse cursor above the target approximately height of the bar.įri, 04:32:27 GMT - Antoine Martin: attachment set I'm using the following monitor configuration: When application window is on the middle monitor then its menus opens on the right side of the leftmost monitor.

TRANSIENT MULTIMON MANAGER DRIVERS

I've managed to track down a set of NVidia drivers that makes the monitor mostly work.In 0.12.2 I found a regression from 0.11.x: in kmail menus open properly only on leftmost monitor. But I've lost a couple of hours trying to find out why something which should just be plug and play is nothing of the sort.

TRANSIENT MULTIMON MANAGER DRIVER

The Nvidia display driver doesn't even let me change options and Vista seems quite happy that nothing is wrong.Īs for me, the picture is so good that I'm just about prepared to live with it for now. The HP monitor control program refuses to believe that an HP monitor is plugged in. The monitor has the habit of reporting itself to Vista as one of a number of devices. And if you are such an idiot as to put the machine to sleep you can look forward to no screen, a black screen with a cursor, a screen that you can't do anything with because the window is on the other screen or the blue screen of death when you come back depending on the whim of the system. Should you be stupid enough to let the screen saver kick in it then does something else. What happens is that you set it up once, and next time you plug it in the system does what the heck it likes, with a range of implausible and hard to select display options.