- Oct 15, 2015
-
-
Marco Trevisan authored
In theory we should have used profiles settings for this, providing a proper unity.ini But right now there's no reason for that effort. In case someone wants to change settings, profiles will fix this.
-
- Oct 09, 2015
-
-
Marco Trevisan authored
In theory we should have used profiles settings for this, providing a proper unity.ini But right now there's no reason for that effort. In case someone wants to change settings, profiles will fix this.
-
- 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
-
- Jun 28, 2013
-
-
Sam Spilsbury authored
-
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 26, 2013
-
-
Sam Spilsbury authored
-
Sam Spilsbury authored
In the event that a window is unreparented or destroyed, we usually need to add its frame window to the toplevel window stack until the time at which we recieve a DestroyNotify for it, as there may be incoming ConfigureNotify events puporting to stack other windows relative to that frame. However, this does not apply in the case where we have not yet received a CreateNotify for the frame window. In that case, it is not possible for any stacking requests to be made relative to this window, so it does not need to be added immediately. Instead, we can add it at the time that we recieve a CreateNotify for it as a regular override redirect window until the time that it is later destroyed. (LP: #1171314)
-
Sam Spilsbury authored
Test that compiz' internal stack representation does not become confused when a a client window is marked as destroyed just before the ReparentNotify arrives. The parent window should not be added to the window stack twice, and instead by added only once when we recieve a CreateNotify for it. As such, restacking the parent window toward the bottom of the stack should result in any dependent stacking operations suceeding and not being mistakenly placed at the top of the stack.
-
- Jun 22, 2013
-
-
Sam Spilsbury authored
PixmapDecoratedWindowAcceptance. UndecoratedWindowExpandToOrigSize Test that upon undecoration, the window has exactly the same geometry as it did before decoration. DISABLED_UndecorateStaticGravityWindow Tests that for windows with a static gravity, the window has exactly the same geometry as it did before decoration. Disabled, as core is currently not moving the window with the static gravity back to where it started. AdjustmentExtents/PixmapDecorationAdjustment. AdjustRestoredWindowBorderMovesClient/P Test that changing the border extents causes the client window's absolute geometry to change. DISABLED_AdjustRestoredWindowBorderShrinkClient/P Tests that changing the border extents causes the client window's absolute geometry to shrink by the amount of border. Disabled, as the current behavior is to expand the frame window as opposed to shrinking the client (but this will be changed). DISABLED_ClientExpandsAsBorderShrinks/P Tests that as the border shrinks away, the client expands back to its original size. Disabled, as the current behavior is to expand the frame window as opposed to shrinking the client (but this will be changed). DISABLED_ClientExpandsAsBorderShrinksWhilstMaximized/P Tests that even if the client is maximized, if the restored border shrinks away it demaximizes back to the same position while also accounting for any change in the restored window border size. Disabled, as the current behavior is to expand the frame window as opposed to shrinking the client (but this will be changed). DISABLED_ClientExpandsAsBorderShrinksWhilstUndecorated/P Tests that even when the client is not permitted to be decorated because the decoration hint was removed, when it is redecorated it will be moved to the correct position taking into account any changes in its border size. Disabled, as the current behavior is to expand the frame window as opposed to shrinking the client (but this will be changed). DISABLED_AdjustRestoredWindowInputNoMoveClient/P Tests that adjusting the input extents (as independent from the border extents) of the client does not cause the client to move. Disabled, as this behavior appears to be broken in core. Move the "GetImmediateParent" function into the compiz::testing namespace so that it can be used by other tests.
-
- May 10, 2013
-
-
Sam Spilsbury authored
Provide our own compiz_xorg_gtest_main and subclass xorg::testing::Environment to try and launch tests on another display if there's tests running on one already. This isn't by any means perfect - there are still race conditions surrounding XOpenDisplay and parallel test runs but it makes any time gap for conditions such as: 1. Client has a server grab on the display we're checking and won't let go. 2. Two servers get launched on one port and one set of tests interfere with the other. It also means that we're now unable to configure the display port, log file and config file on the command line. But we weren't using that anyways. Finally, the logs now point to /tmp/Compiz.Xorg.GTest.displaynum.log (LP: #1178514)
-
- Apr 22, 2013
-
-
Sam Spilsbury authored
included in everything.
-
- Apr 02, 2013
-
-
Łukasz 'sil2100' Zemczak authored
As recommended by Sam, let's divide the one helper function into two smaller ones and create the tests using those helpers.
-
Łukasz 'sil2100' Zemczak authored
To avoid too much code duplication, export the new test code into a helper method and use it to execute the 4 newly added tests.
-
Łukasz 'sil2100' Zemczak authored
Thanks Sam for pointing this out! It seems we were missing a mask for the override_redirect attribute in XCreateWindow()!
-
- Mar 29, 2013
-
-
Łukasz 'sil2100' Zemczak authored
-
- Mar 26, 2013
-
-
Łukasz 'sil2100' Zemczak authored
-
- Mar 21, 2013
-
-
Łukasz 'sil2100' Zemczak authored
-
- Mar 06, 2013
-
-
Sam Spilsbury authored
the frame window size, don't just use the difference in frame extents to determine that. (LP: #1140505)
-
Sam Spilsbury authored
that variable only exists to track changes in the actual geometry of the window and not the apparant frame extents. Added tests to verify that behaviour. (LP: #1138517)
-
- Feb 26, 2013
-
-
MC Return authored
-
Sam Spilsbury authored
-
- Feb 20, 2013
-
-
Sam Spilsbury authored
-
- Feb 19, 2013
-
-
Sam Spilsbury authored
-
- Feb 15, 2013
-
-
Sam Spilsbury authored
This is really going thermonuclear on these failing tests :(
-
- Feb 14, 2013
-
-
Sam Spilsbury authored
-
Sam Spilsbury authored
-
Sam Spilsbury authored
and then make sure that the window and frame geometry are as expected
-
Sam Spilsbury authored
configure a window and get a response back
-
Sam Spilsbury authored
startup message so we can interact with it
-
Sam Spilsbury authored
to hold on to the atoms for common protocol messages for the tests, created some utility functions to send and wait for ClientMessage events and also added a new failing test for loading plugins from dir specified in an environment variable
-
- Feb 13, 2013
-
-
Sam Spilsbury authored
be used to communicate with the tests in order to make compiz do certain things
-
- Feb 12, 2013
-
-
Brandon Schaefer authored
-
Sam Spilsbury authored
-
Sam Spilsbury authored
behind their own functions. Make it so that all users can see xorg-gtest and not just the users in tests/
-
- Feb 10, 2013
-
-
Sam Spilsbury authored
(LP: #1120009)
-
- Jan 16, 2013
-
-
Sam Spilsbury authored
-
- Jan 11, 2013
-
-
Sam Spilsbury authored
-
Sam Spilsbury authored
-
Sam Spilsbury authored
option values
-
Sam Spilsbury authored
that XShape is disabled. Verify the behaviour with a new set of system tests. (LP: #729979)
-