We are experimenting with multi-touch client/host instead of the regular
Windows mouse interface. Getting WM_TOUCH type messages into the client with
the multiple touch points is easy but the approach for how to support these in
the server (Spice/QEMU) and the guest OS raises some questions. It
As an outside observer with nothing really at stake here, it would seem that
rather than Debian providing a hobbled version of the spice client that uses
raw audio (disables Celt), they offer up a patch for both the server and the
client that implements a negotiation for either Opus or Celt (for
Not sure if this applies since I'm looking at the spice-gtk 0.11 source, but
the generated_demarshallers.c code includes a function parse_SpiceMsgEmpty.
Within it it uses "sizeof(SpiceMsgEmpty)" and some pointer/allocator math for
demarshalling a SpiceEmptyMsg. I'm no expert here, but I would th
There's been a lot of work/effort moving the protocol handling,
marshalling/demarshalling code, etc to a common submodule. I also saw several
references over the last few weeks/month on the tunnel channel and the
smartcard channel, in particular on how those modules may be out of date ("bit
rot
You will either need to upgrade your gcc to a newer version that supports
vala or you will need to install the valac compiler.
If you want to use the valac compiler: sudo apt-get install valac
Afterwards, configure the spice build with --enable_vala=yes
Brian
On Fri, Mar 2, 2012 at 6:48 AM, Naga
I'm new to Spice and have been looking over the spice_gtk sources, trying to
piece together all that is there. I saw that in the common directory, there are
a collection of gl*.[ch] files look to be opengl client rendering services,
presumably used instead of the sw*[ch] and Windows gdi files. H
