search for: compwindow

...at can be easilly used in plugins. -------------- next part -------------- diff --git a/include/compiz.h b/include/compiz.h index 61a9de5..ccce7c3 100644 --- a/include/compiz.h +++ b/include/compiz.h @@ -1245,6 +1245,14 @@ typedef void (*SetWindowScaleProc) (Comp typedef Bool (*FocusWindowProc) (CompWindow *window); +typedef void (*WindowCreateNotifyProc) (CompWindow *window); + +typedef void (*WindowDestroyNotifyProc) (CompWindow *window); + +typedef void (*WindowMapNotifyProc) (CompWindow *window); + +typedef void (*WindowUnmapNotifyProc) (CompWindow *window); + typedef void (*WindowResizeNotify...

Hi, The attached core patch makes the 'isFocussable' getter in CompWindow wrappable. This way, plugins such as winrules can make core's getter function return a different value to the one stored internally without actually having to modify the value. Kind Regards, Sam -- Sam Spilsbury -------------- next part -------------- A non-text attachment was scrubbed... N...

...r 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; end = 65535.0f; @@ -518,15 +521,20 @@ findNextWestEdge (CompWindow *w, x = object->position.x + w->output.left - w->input.left; - if (x >= w->screen-&g...

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 & MAXIMIZE_STATE) flags &= ~(PResizeInc | PAspect); } After playing with that, however, I wond...

...(w); } else - focusDefaultWindow (d); + focusDefaultWindow (d->screens); } d->pingHandle = @@ -2565,45 +2565,41 @@ getCurrentTimeFromDisplay (CompDisplay *d) } void -focusDefaultWindow (CompDisplay *d) +focusDefaultWindow (CompScreen *s) { - CompScreen *s; CompWindow *w; CompWindow *focus = NULL; - for (s = d->screens; s; s = s->next) + for (w = s->reverseWindows; w; w = w->prev) { - for (w = s->reverseWindows; w; w = w->prev) - { - if (w->type & CompWindowTypeDockMask) - continue; + if (w->type & CompWindo...

...vent); +typedef void (*HandleCompizEventProc) (CompDisplay *display, + char *pluginName, + char *eventName, + CompOption *option, + int nOption); + typedef Bool (*CallBackProc) (void *closure); typedef void (*ForEachWindowProc) (CompWindow *window, @@ -749,7 +755,8 @@ struct _CompDisplay { InitPluginForDisplayProc initPluginForDisplay; FiniPluginForDisplayProc finiPluginForDisplay; - HandleEventProc handleEvent; + HandleEventProc handleEvent; + HandleCompizEventProc handleCompizEvent; CompPrivate *...

...d decoration" around the window decoration. The question now is: How can we communicate the fact that there is a second set of decoration properly to other plugins so that window damaging and transformation are aware of the glow? >From my understanding, the member "output" of the CompWindow structure is supposed to do exactly that. But its contents get overwritten by the decoration plugin on every window state change and window activation/deactivation, so our plugin can't use it (and the function setWindowFrameExtents) directly because the changes aren't persistent. Is there...

...t>, w=0x1e67540) at decoration.c:1343 No locals. #14 0x000000000042380a in windowInitPlugins (w=0x1e67540) at plugin.c:391 p = (CompPlugin *) 0xcc1cb0 #15 0x000000000041c918 in addWindow (screen=0x7be910, id=<value optimized out>, aboveId=20989985) at window.c:2132 w = (CompWindow *) 0x1e67540 #16 0x000000000041e832 in handleEvent (d=0x633f00, event=0x7fff0f24ad30) at event.c:1249 raise = <value optimized out> delay = <value optimized out> s = (CompScreen *) 0x7be910 w = <value optimized out> #17 0x00002aaaacac355d in thumbHa...

Me and Dennis Kasprzyk changed CompRect to be more intuitive and easily replace XRectangle use. This patch changes CompRect and whole Core. Thanks for attention. -- Eduardo Gurgel Pinho (GELSoL-UFC) (Gentoo) Linux User #415930 http://edgurgel.wordpress.com http://alu.dc.ufc.br/~eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL:

...just having functions that apply changes. This is better as it allow each plugin to execute something both before and after the change has been applied. Example: Instead of wrapping a windowStateChangeNotify function you would wrap a changeWindowState function static void pluginChangeWindowState (CompWindow *w, int state) { int oldState = w->state; PLUGIN_SCREEN (w->screen); if ((oldState ^ state) & STATE_PLUGIN_CARE_ABOUT_MASK) { /* do something interesting */ } UNWRAP (ps, w->screen, changeWindowState); (*w->screen->changeWindowState) (w, sta...

Hi all, attached is a patch which extends the window resize notify function: Instead of just passing the CompWindow*, additionally the resize difference information is passed (difference of position, width and height). Originally, I wrote this one for Beryl as we needed it for the group plugin, but I think it makes sense that Compiz also has this for the sake of plugin interoperability; especially as the move no...

...t values on inactive windows. The plugin is very simple and the main part is below. When I load this plugin it blocks dbus and fuse plugins so that they only reply to requests when the active window changes. Is there anything obvious here that would cause that? static Bool inactivePaintWindow (CompWindow *w, const WindowPaintAttrib *attrib, const CompTransform *transform, Region region, unsigned int mask) { Bool status; INACTIVE_SCREEN (w->screen); INACTIVE_WINDOW (w); WindowPaintAttrib fAttrib = *attrib; if (iw-&...

...memory leaks. Minor cleanup. Fix another mem leak. Plug some minor memory leaks. Warning fix. Revert "Update default window match to account for panel selection mode." Evaluate window match only for non-panel selection mode. Store icon geometry in CompWindow struct. Bump ABIVERSION. Use icon geometry stored in CompWindow struct. Fix some minor memory leaks. Don't focus default window when rotating due to window activation. Add missing glib includes. Revert "Don't focus default window when rotating due to...

...t in Compiz and which I believe Compiz should have, too: - Remembering of the last window state inside the state change notify This is useful for properly tracking down the window state changes (e.g. has the window been maximized in that state change?). In Beryl, we added a variable lastState into CompWindow, which is updated inside core's stateChangeNotify. The attached last-window-state.patch brings that behaviour to Compiz. - Remembering the grabbing state Previously, only one window could be grabbed at a certain time. However, when using group, a number of windows can be grabbed at a certain t...

Hi, There are a couple of problems with Snapping Windows that I tried to fix: (1) The snap to windows checkbox in ccsm has no effect because Snap treats any window with struts as an edge, and all windows have struts. I think it should be a test for dock windows. (2) Windows don't snap to the left edge because it has been erased. The right edge doesn't seem to get erased because it is

...t, so you can see the typing in the A window through it. In this case, after full-screen is turned off, the window is passed to updateWindowAttributes() with the stackingMode=CompStackingUpdateModeNormal. (The problematic call is in the file "extrawm.c"). The function is fullscreenWindow(CompWindow*, int). At the end (line 71 in my version) there's a call to updateWindowAttributes (w, CompStackingUpdateModeNormal) However, changing from full-screen to non-full-screen should not change the stacking. So I believe the call should be changed to: updateWindowAttributes (w, Com...

--- src/window.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/src/window.c b/src/window.c index 568373d..2133aed 100644 --- a/src/window.c +++ b/src/window.c @@ -2227,6 +2227,11 @@ destroyWindow (CompWindow *w) w->id = 1; w->mapNum = 0; + if (w->shaded) + { + updateClientListForScreen (w->screen); + } + w->destroyRefCnt--; if (w->destroyRefCnt) return; -- 1.5.2.5 --dDRMvlgZJXvWKvBx Content-Type: text/x-diff; charset=us-ascii Content-Disposition: at...

With raise_on_click disabled, I wanted to be able to raise a window with a button click sometimes. It seemed logical to do something like the lower window key binding. So I did it. It was quite simple, but here is the patch anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 3680 bytes Desc: not available

Here is a bug that make me insane since a lot of time. Randomly, when launching an kde application, i can see it appear on screen and then being placed by place plugin. I look at place plugin code and everything looks ok... http://hibbert.univ-lille3.fr/~cbellegarde/PlacementBug.png Here a screenshot of the bug, as you can see, window first appear at this "non placed" position, then, it

...gt; Could someone give me a quick example of the usage as I would like to > finalize > the animation porting. I looked at the second version you sent to the list on October 4. To make the plugin compile without the patches to Compiz core, I moved the new fields from the public CompScreen and CompWindow to the private AnimScreen and AnimWindow respectively. Similarily, I moved their initialization to the functions where those structures are allocated in the plugin. I tried to keep the changes to minimum and have a patch attached plus the resulting animation.c. Based on short testing it runs at le...