- Oct 15, 2015
-
-
Marco Trevisan authored
This shouldn't be needed anymore as it was a temporary fix for LP:1127866
-
Marco Trevisan authored
-
- Oct 09, 2015
-
-
Marco Trevisan authored
This shouldn't be needed anymore as it was a temporary fix for LP:1127866
-
Marco Trevisan authored
-
- Jul 23, 2015
-
-
Stephen M. Webb authored
-
Stephen M. Webb authored
-
- Apr 29, 2015
-
-
Eleni Maria Stea authored
-
- Apr 27, 2015
-
-
Eleni Maria Stea authored
when the 3d clipping is performed
-
- Apr 07, 2015
-
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
- Mar 30, 2015
-
-
Stephen M. Webb authored
-
Stephen M. Webb authored
-
Stephen M. Webb authored
-
Stephen M. Webb authored
-
- Mar 12, 2015
-
-
Eleni Maria Stea authored
replaced glLoadIdentity(); glMultMatrix... with glLoadMatrix, there's no need to multiply the 2nd matrix with the identity before the loading
-
- Mar 02, 2015
-
-
Eleni Maria Stea authored
perform vector operations (additions/multiplications etc) otherwise the transformations won't be correct. If we include the w value in the addition etc we might have unexpected projections (when w > 1) and divisions by 0 (when w = 0) because opengl divides the x,y,z values by w.
-
- Feb 26, 2015
-
-
Chris Townsend authored
-
- Dec 10, 2014
-
-
Christopher Townsend authored
-
Christopher Townsend authored
Move a updateXToGLSyncs() call to the correct place due to a bad merge.
-
Stephen M. Webb authored
-
- Dec 09, 2014
-
-
James Jones authored
Use the GL_EXT_x11_sync_object OpenGL extension to synchronize updates with X11 to avoid unrefreshed parts of the screen on Nvidia hardware.
-
- Oct 30, 2014
-
-
Stephen M. Webb authored
-
- Mar 03, 2014
-
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
This seem to cause also a crash when using software rendering.
-
- Dec 04, 2013
-
-
Povilas Kanapickas authored
OpenGl: Run the opacity filter after all other filters have been run. Fixes https://bugs.launchpad.net/compiz/+bug/1257223.
-
- Oct 31, 2013
-
-
Eleni Maria Stea authored
methods don't have virtual destructors, added the virtual destructors to get rid of warnings and potential memory leaks
-
- Aug 19, 2013
-
-
James Jones authored
once they are no longer current to any thread. To ensure the context really is destroyed, lose current from it before destroying it.
-
- Jul 17, 2013
-
-
Sam Spilsbury authored
-
- Jul 15, 2013
-
-
Andrea Azzarone authored
-
- Jun 28, 2013
-
-
Sam Spilsbury authored
1. Completely remove decorOffsetMove and other related code from decor.cpp. Put the logic to handle the window->input () - window->border () placement offset inside of setWindowFrameExtents instead. Now the window will always be offset from its original non-decorated position to the new decorated position, rather than having to guess between decoration sizes. 2. Make saveGeometry and restoreGeometry work relative to window->border () as opposed to including it in the saved geometry. It is possible that the border size might change during maximization, as such, we don't want to save the position with the border before maximizing. Instead save the position as if it were never decorated so that when the window is restored it can be restored to its original position and then adjusted for its new border size. 3. Fix a few typoes in the tests. 4. Moved some commonly used matchers into compiz::testing 5. Make COMPIZ_PLUGIN_DIR accept multiple directories and look in each one of them for the plugin 6. Set COMPIZ_PLUGIN_DIR appropriately for each plugin that we wish to load on startup so that we load locally built plugins as opposed to installed ones. 7. Uncomment compiz_discover_tests for the acceptance tests. Now they are run by default.
-
- Jun 10, 2013
-
-
Sam Spilsbury authored
textures changed.
-
- May 15, 2013
-
-
Marco Trevisan authored
-
- May 14, 2013
-
-
Marco Trevisan authored
-
- May 13, 2013
-
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
This fixes a crash with new MESA drivers and high monitor resolutions caused by the fact that we're accidentally using some MSAA configs with some drivers in Mesa 9.0. Taking in account the values of GLX_SAMPLES and GLX_SAMPLE_BUFFERS fixes the issue. See mesa bug https://bugs.freedesktop.org/show_bug.cgi?id=61182
-