search for: _net_workarea

...f multiple monitors (and thus currently ignored as struts in the output workarea setup). I personally think we should include these "inner" struts when calculating the workarea for each output (which also helps window maximizing), and only ignore them in the screen workarea case (for the _NET_WORKAREA hint). Any reason that wouldn't make sense? ...MC -------------- next part -------------- --- plugins/wobbly.c +++ plugins/wobbly.c @@ -510,6 +510,9 @@ findNextWestEdge (CompWindow *w, int e, end; int x; + int output; + XRectangle workArea; + start = -65535.0f;...

Hey, I'm thinking about the addition of the getWorkareaForOutput method, and I'm wondering if it wouldn't make sense to define the workarea as part of the CompOutput struct and set it up as part of (or replacing?) the updateWorkareaForScreen call. Either that or make the call to getWorkareaForOutput redo the extents calculation on the windows within only that output. Which do you

Hi David, When maximizing windows on a different resolution only 70% of the window is maximized. Ie: on my 1280x1024 screen a window maximized is correct (and does not clobber the desktop panel in KDE, kicker) On my 1600x1200 screen, with no kicker panel, the window is maximized about 70% of the screen only Is this known? Thanks, Shawn. ----- Original Message ---- From: David Reveman

...he NO_UI flag in ShellExecute. shell32: Display error messages in ShellExecuteEx. shell32: Use ShellExecuteEx instead of ShellExecute in the run dialog. shell32: Use ShellExecuteEx to create error dialogs for the run dialog. winex11.drv: Do not assume window managers support _NET_WORKAREA. Vitaliy Margolen (1): dinput: Remove DIEnumDevicesCallbackAtoW. Wolfgang Walter (1): wineps.drv: Fix freeing of not allocated memory in type42.c. -- Alexandre Julliard julliard at winehq.org