~vanvugt/compiz-core/tapping-panacea : changes

~vanvugt/compiz-core/tapping-panacea » Changes from revision 3050

From Revision 3026 to 3007

Rev	Summary	Authors	Date
3026	Add test cases for CompRegionRef. Add test cases for CompRegionRef.	Alan Griffiths	12 years ago
3025	Fixes an issue with recording of properties in unit tests re... Fixes an issue with recording of properties in unit tests resulting in invalid XML	Alan Griffiths	12 years ago
3024	Avoid uninitialized memory reads, which could lead to unpred... Avoid uninitialized memory reads, which could lead to unpredictable results. The uninitialized memory was in the padding bytes of imperfectly aligned structures. (LP: #940066)	Daniel van Vugt	12 years ago
3023	DOUBLED the CPU performance of compiz. Previously compiz was... DOUBLED the CPU performance of compiz. Previously compiz was spending about 51% of its time constructing and destructing CompRegions. This proposal reduces that figure to about 4.4%, resulting in a net reduction in compiz CPU usage of almost 47%. And it is noticeable too. (LP: #940139)	Daniel van Vugt	12 years ago
3022	PrivateScreen tests reworked to reflect recent split up of PrivateScreen tests reworked to reflect recent split up of PrivateScreen.	Alan Griffiths	12 years ago
3021	Detect unresolvable symbols at load time (and so fail gracef... Detect unresolvable symbols at load time (and so fail gracefully), instead of waiting till run-time and allowing them to cause a crash. (LP: #938478)	Daniel van Vugt	12 years ago
3020	Fix memory leak (LP: #940115) Fix memory leak (LP: #940115)	Alan Griffiths	12 years ago
3019	Split out the bits of PrivateScreen that don't depend on hav... Split out the bits of PrivateScreen that don't depend on having a Display.	Alan Griffiths	12 years ago
3018	Avoid SIGSEGV in XDefineCursor() when display fails to initi... Avoid SIGSEGV in XDefineCursor() when display fails to initialize. (Bug #936487)	Alan Griffiths	12 years ago
3017	Check if the mutter key exists before using it. This fixes t... Check if the mutter key exists before using it. This fixes the lack of draggable borders if mutter isn't installed. (LP: #936781)	Sam Spilsbury	12 years ago
3016	Fix keyboard lockup, which occurred when a plugin was deviou... Fix keyboard lockup, which occurred when a plugin was devious enough to override handleEvent and not allow keyboard events to reach core. (LP: #934058) Arguably we should fix the offending plugin (unityshell). But I figured it's better to make core more robust so that the same bug can never occur with any plugin in future.	Daniel van Vugt	12 years ago
3015	Remove dead code (extern declarations of non-existent global... Remove dead code (extern declarations of non-existent globals).	Daniel van Vugt	12 years ago
3014	Delete dead code. Delete dead code.	Alan Griffiths	12 years ago
3013	Fix typo which would cause maximized windows to not receive ... Fix typo which would cause maximized windows to not receive shadows at all	smspillaz	12 years ago
3012	Also update state, actions and icon whenever the window beco... Also update state, actions and icon whenever the window becomes redecorated as those may have changed while the window was undecorated Merge lp:~smspillaz/compiz-core/compiz-core.fix_936778 into lp:compiz-core	smspillaz	12 years ago
3011	Don't silently let windows that we couldn't find a sibling b... Don't silently let windows that we couldn't find a sibling below for sit at the top of the stack (LP #936675) If we couldn't find a sibling for the window upon initial map, then it means that it needs to be placed at the bottom of the stack, since there could be windows above it which should not be below the newly created window. Fixes a case where on startup, nautilus could be slow to load and new windows would be created before nautilus was, and those would go above panels incorrectly. Merge lp:~smspillaz/compiz-core/compiz-core.fix_936675 into lp:compiz-core	smspillaz	12 years ago
3010	Only call removeAction on the CompOption destructor and not ... Only call removeAction on the CompOption destructor and not the CompOption::Value destructor, since plugins that make copies of CompOption::Value can cause actions to be added through setOptionForPlugin and then those actions will be removed when the value temporary goes away. The action adding and removing only happens within the bounds of CompOption anyways, so its its more appropriate to have it in its destructor. Of course, this brings up another issue, which is that CompOption should be noncopyable but this opens up a whole another can of worms. How this even worked before is beyond me... Merge lp:~smspillaz/compiz-core/compiz-core.fix_931927 into lp:compiz-core	smspillaz	12 years ago
3009	Fixes the state atoms never being unset if no bits were bein... Fixes the state atoms never being unset if no bits were being set. This fixes the previous commit, which was a fix for LP: #932087.	Sam Spilsbury	12 years ago
3008	Refactor out fillStateData since it was being duplicated in ... Refactor out fillStateData since it was being duplicated in a plugin that was causing bug 932087. (LP: #932087)	Sam Spilsbury	12 years ago
3007	Fix untranslated strings - Add missing files to POTFILES.in.... Fix untranslated strings - Add missing files to POTFILES.in. (LP: #780505)	Gabor Kelemen	12 years ago