search for: mcook

Michael R. Cook, GCFW Network Security Specialist Norton Healthcare, Information Services 502-629-8034 mcook@nortonhealthcare.org <mailto:mcook@nortonhealthcare.org> ----------------------------------------- This message is confidential, intended only for the named recipient(s) and may contain information that is privileged or exempt from disclosure under applicable law. Any patient health in...

On Thursday 08 February 2007 01:00:09 Bellegarde Cedric wrote: > And now, i put the patch on my server, it will me prevent me to send you a > message everytime i find something to fix ;) > > http://puffy.homelinux.org/~gnumdk/compiz/patch/place.patch http://forum.go-compiz.org/viewtopic.php?p=3783 Seems to be buggy in multihead, but i can't test here ... Cedric

...manually going through the git history as I've always included the authors name in the commit message but it would save me some time if people could instead reply to this mail if they've done contributions that are not listed below. Thanks, -David ------------------ Author: Mike Cook <mcook@novell.com> Only hide windows on current output. Add initiate_output action, which initiates scale mode only for windows visible on current output. Compute xTranslate and yTranslate correctly for output specific zoom. Author: Mike Dransfield <mike@blueroot.co.uk> Add a...

Here's a couple quick patches to resolve some minor issues related to multiple outputs that I bumped into today. nodetectfix.patch: Enables reading outputs config (instead of 640x480 default) when using "--no-detection" switch but config says detect. constrainyoutput.patch: Allows full vertical workarea to be used in the case of multiple vertical outputs. Currently it won't

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

Hey, David, with the latest changes for output-specific zoom it wasn't focusing properly for me with mixed resolutions. I think this patch corrects that. (Oh, and on my previous comment I meant struts and not extents, if that was confusing to anyone. It was to me when I re-read it, heh.) ...MC -------------- next part -------------- --- plugins/zoom.c +++ plugins/zoom.c @@ -480,8 +480,12

Here's a quick patch to have either horz or vert (instead of both) maximized windows honor the "ignore" option: --- src/window.c +++ src/window.c @@ -4012,7 +4012,7 @@ constrainNewWindowSize (CompWindow *w, if (d->opt[COMP_DISPLAY_OPTION_IGNORE_HINTS_WHEN_MAXIMIZED].value.b) { - if ((w->state & MAXIMIZE_STATE) == MAXIMIZE_STATE) + if (w->state

Since I first tried nVidia's AIGLX with Compiz I've been seeing some pretty consistent drawing problems on GWD's minimize and maximize buttons on hover. It looks like part of the fill is drawn with low alpha. I haven't been able to duplicate it when using Xgl... Here's a quick vid of what I'm seeing:

Hey, David, for me the recent multihead changes had minor a problem with mixed resolutions (1600x1200 & 1280x1024). The viewport was getting set partially off screen. The following tweak fixed it for me: --- plugins/display.c +++ plugins/display.c @@ -2069,7 +2069,7 @@ eventLoop (void) { if (s->nOutputDev > 1)

I am having difficulties installing the RMySQL package (0.6-1) on a clean install of pclinuxos with R version 2.5.1. My version of the OS came with R-base already installed along the RKWard GUI front end.I have attempted to install the package through RKWard however I have had some problems. I have searched google and various forums extensively but I have not found anyone with the exact same

Here's a patch to wobbly.c to handle edge snapping with multiple outputs... Also, I tweaked the window edge snapping to include dock window types, to support the case where dock windows may be on the inner edges of 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