in compiz

with a buffer size of 128, as the definition says char buf[128]

Followed a recommendation of Coverity and replaced sprintf () with snprintf () with a buffer size of 128, as the definition says char buf[128]

Followed a recommendation of Coverity and replaced sprintf () with snprintf () with a buffer size of 128, as the definition says char buf[128]

functions that we wanted to get under test, write tests for them too

It was a broken hack for a problem that didn't exist

This removes two fixes (LP: #454218) (LP: #929989)

failures on decorations during normal resize

The uninitialized memory was in the padding bytes of imperfectly aligned
structures. (LP: #940066)

Merged -r2983..2985 from lp:~smspillaz/compiz-core/compiz-core.decor_928173

race between the decorator and the decor plugin when attempting to bind a pixmap
that hasn't been fully formed yet. (Should really use XSync barriers in future)

multiple default frame styles) and also to allow decorators to specify
in the frame property which window types, states and actions the frames
should apply to

Rationale: some window decorators or themes might want to specify a border
input area that is slightly larger than the visible borders on screen
(eg for enhanced resize handles, a11y purposes, etc) or the theme might
want to specify some additional decoration which should affect placement
but should not be interacted with.

In this case we have a priv->border and priv->input window property.
priv->border specifies the actual semantic size of the window decoration
that should affect placement and priv->input specifies the extents of
the frame window past the client.

Fixes LP: #710271

- Use a separate frame window for decorations.

The new ignore_src_alpha parameter tells libdecoration to ignore the alpha channel of the src picture.

If those atom names do not match between decorator and decoration plugin, the decorator will be useless; so it makes sense to include them in the interface.

required libraries.