x11: Don't ignore button releases after a wmspec move/resize

_gdk_x11_moveresize_configure_done() isn't called for wmspec
moves/resizes so we don't have a way to notice when a wmspec
move/resize ends and consequently untrigger the sending of
_NET_WM_MOVERESIZE_CANCEL which results in this message always being
sent on the next button release event. In that case we are marking
that event as handled so it isn't processed further which breaks
button press/release event handling in several widgets.

To fix this we simply allow the normal event handling machinery to run
after sending the _NET_WM_MOVERESIZE_CANCEL message.

https://bugzilla.gnome.org/show_bug.cgi?id=673328
paned: Shrinkable widgets don't require a size

This could otherwise lead to very funny size request behaviors, in
particular in empathy.

https://bugzilla.gnome.org/show_bug.cgi?id=587441
Updated Odia Translation
gtk: Don't call gdk_window_process_updates() when scrolling

This can cause lagging when scrolling as it causes us to repaint
on every scroll event. This wasn't historically a great problem,
but with smooth scrolling we get a lot more events, so this
now creates visible lagging on slower machines.
Update gdk-win32 Visual C++ projects

A new source file gdkdevice-virtual.c was added in commit 24f9ca92 for the
Win32 GDK backend, so add that file to the list of source files to compile.
Update libgail-util Visual C++ projects

Make the output .lib name more consistent with the GDK/GTK+ output .lib
naming.
xi2: Remove touchscreen heuristics

It doesn't make sense to consider a device a touchscreen if it
doesn't have any touch classes. Even if it has 'touch' in its
name.
https://bugzilla.gnome.org/show_bug.cgi?id=673440
Don't force BUTTON1_MASK on non-touch events

This problem was pointed out by Hans de Goede in
https://bugzilla.gnome.org/show_bug.cgi?id=673458
x11: Add suggested braces around empty body in 'if' statements
win32: Move variable declarations into #if block
tray: Add suggested braces around empty body in 'if' statements
menu: Undo a hack with style contexts

Widget implementations aren't allowed to fiddle with the widget's style
context.

Sheesh.
widget: Create style context using regular API
treeview: Don't cache expander size

Style properties should not be cached, they should be queried live.

Also, this fixes the case where the expander size wasn't set when
constructing the widget which caused expanders to go missing.
docs: Add gtkx.h to the list of headers
csscomputedvalues: Unref old value when setting new one
textview: Remove extra magic for drawing children

Instead, just draw the children. The cairo code will keep track of
things, so there's no need to track things.
Also, the old code was doing it wrong.

https://bugzilla.gnome.org/show_bug.cgi?id=672544
entrycompletion: set_property() should call property setters

gtk_entry_completion_set_property() was setting many properties by
directly modifying priv values, bypassing notification invocation and
possibly another actions done by gtk_completion_entry_set_xxx ()
functions.  Fix by invoking set_xxx() instead of setting the property
value directly.

The real bug observerd was that setting text-column property using
g_object_set() caused SIGFPE later when entry completion was about to
appear.  gtk_entry_completion_set_text_column () apparently does way
more important things than just setting priv->text_column member.

https://bugzilla.gnome.org/show_bug.cgi?id=673693
cssvalue: Re-add support for random value types

This got lost in the CssValue transition, and apparently some people use
this.
tests: Add a uint8 test

... to ensure the last test works.