New experimental API is added to allow changing the way that redraws
are timed for a stage to include a "sync delay" - a period after
the vertical blanking period where Clutter simply waits for updates.

In detail, the algorithm is that when the master clock is restarted
after drawing a frame (in the case where there are timelines running)
or started fresh in response to a queued redraw or relayout, the
start is scheduled at the next sync point (sync_delay ms after the
predicted vblank period) rather than done immediately.

https://bugzilla.gnome.org/show_bug.cgi?id=692901

In commit 8f4e39b6 the Wayland code was updated to use the new
xkbcommon API. This involved changing the common XKB code shared with
the evdev input backend. However the evdev input backend was not
modified so it wouldn't compile. This patch just makes a minor change
to update it.

https://bugzilla.gnome.org/show_bug.cgi?id=693348

(cherry picked from commit d0d1b562)

accessible->name is eventually freed, so we need to dup the string
to ensure that everything is alright.

This is needed for the buffer_age changes.

https://bugzilla.gnome.org/show_bug.cgi?id=669122

Use the buffer_age extension when available to recycle backbuffer contents
instead of blitting from the back to front buffer when doing clipped redraws.

The picking is now done in a pixel that is going to be repaired during the next
redraw cycle for non static scences.

This should improve performance and avoid tearing.

Reviewed-by: Robert Bragg <robert@linux.intel.com>

https://bugzilla.gnome.org/show_bug.cgi?id=669122

This allows us to report to the backend that the stage's back buffer has been trashed
while handling picking. If the backend is keeping track of the contents of back buffers
so it can minimize how much of the stage is redrawn then it needs to know when we do pick
renders so it can invalidate the back buffer.

Based on patch from Robert Bragg <robert@linux.intel.com>

https://bugzilla.gnome.org/show_bug.cgi?id=669122

A slave is associated to a master device, not the other way around.

https://bugzilla.gnome.org/show_bug.cgi?id=692971

Since XIQueryVersion, the bad API that it is, chooses the first client
version that it gets, we need to ensure that we pass XIQueryVersion the
new XI2.3 version, knowing fully well that Clutter won't be confused
by the new features.

https://bugzilla.gnome.org/show_bug.cgi?id=692466

The X server should fill in the minor version that it supports in the
case where it only supports the older version. We should not get a
BadRequest or fail the version check if we pass something higher.

https://bugzilla.gnome.org/show_bug.cgi?id=692466

Signed-off-by: Gheyret Kenji <gheyret@gmail.com>

Signed-off-by: Gheyret Kenji <gheyret@gmail.com>

Tomeu Vizoso authored Dec 26, 2012 and Emmanuele Bassi committed Jan 16, 2013

So code that still uses the deprecated ::swept keeps working

https://bugzilla.gnome.org/show_bug.cgi?id=690735

Kouhei Sutou authored Jan 13, 2013 and Emmanuele Bassi committed Jan 16, 2013

https://bugzilla.gnome.org/show_bug.cgi?id=691651

Nirbheek Chauhan authored Dec 18, 2012 and Emmanuele Bassi committed Jan 16, 2013

The behaviour imitates GtkEntry and ignores attributes from markup because Pango
barfs on invalid markup. Also add an example to the text-field interactive test.

https://bugzilla.gnome.org/show_bug.cgi?id=686477

Wouter Paesen authored Dec 28, 2012 and Emmanuele Bassi committed Jan 16, 2013

* use requested value of fullscreen state in clutter_stage_win32_set_fullscreen instead of old value

https://bugzilla.gnome.org/show_bug.cgi?id=690836

Wouter Paesen authored Dec 28, 2012 and Emmanuele Bassi committed Jan 16, 2013

https://bugzilla.gnome.org/show_bug.cgi?id=690835

Wouter Paesen authored Dec 28, 2012 and Emmanuele Bassi committed Jan 16, 2013

https://bugzilla.gnome.org/show_bug.cgi?id=690833

Kouhei Sutou authored Jan 04, 2013 and Emmanuele Bassi committed Jan 16, 2013

https://bugzilla.gnome.org/show_bug.cgi?id=691114

Jasper St. Pierre authored Jan 14, 2013 and Emmanuele Bassi committed Jan 16, 2013

TRUE and FALSE need to be symbolified here.

A stupid typo broke the linear interpolation function.

As x11 considers num lock and scroll lock to be modifiers, code that
checks for an exact modifier combination will fail if naively done when
num lock or scroll lock are turned on. Applications that want to ignore
these modifiers will need to use XKB to manually mask out the modifier
state.

As it is very unlikely that applications will want to care about the
state of num lock or scroll lock for key press/key release events, mask
out the num lock and scroll lock keys automatically.

https://bugzilla.gnome.org/show_bug.cgi?id=690664

Daniel Stone authored Dec 19, 2012 and Emmanuele Bassi committed Jan 10, 2013

This has been disabled since February 2008, on the grounds that XFixes
didn't work reliably for hiding cursors.  This has almost certainly been
fixed then and seems to work entirely reliably across a number of X
servers released in the past few years, and is definitely better than a
1x1 black dot for a cursor.

Helpfully though, where the spec states that the cursor will be hidden
when inside the specified window or one of its children, it actually
only uses the window to look up the Screen, and hides the cursor across
the entire Screen.  So, when using this, we also need to track crossing
events.

If it's still broken, this needs to be fixed in the X server.

https://bugzilla.gnome.org/show_bug.cgi?id=690497



Signed-off-by: Daniel Stone <daniel@fooishbar.org>

We need to include the gdk-pixbuf headers as well...

Fix the *_GDK configs as GDK headers will include GDK-Pixbuf headers as
well.