Re: [Spice-devel] [PATCH spice-gtk 3/3] Move clipboard handling to SpiceGtkSession

2011-10-04 Thread Marc-André Lureau
Hi, I think you may want to use "self" for SpiceGtkSession variables inside the .c. It would make it more obvious that this is not a gtk symbol and it's also slightly easier to refactor (no clash with function name, no need to rename). This way you avoid the conflict session vs gtk_session. It's q

Re: [Spice-devel] [PATCH spice-gtk 2/3] Add a SpiceGtkSession Class

2011-10-04 Thread Marc-André Lureau
hi On Tue, Oct 4, 2011 at 4:20 PM, Hans de Goede wrote: > This initial commit of the SpiceGtkSession Class only adds the empty > class and the 1:1 linkage to SpiceSession through 2 new private methods > added to SpiceSession: spice_session_{get|set}_gtk_session. > > The following commits will mov

[Spice-devel] [PATCH spice-gtk 3/3] Move clipboard handling to SpiceGtkSession

2011-10-04 Thread Hans de Goede
This fixes copy and paste with multi-monitor guests. There still is one small issue left with this patch, changing the setting for auto-clipboard in one spicy window, does not get reflected in the Options menu of the other spicy windows. This can be fixed by listening to the notify signal, this al

[Spice-devel] [PATCH spice-gtk 2/3] Add a SpiceGtkSession Class

2011-10-04 Thread Hans de Goede
This initial commit of the SpiceGtkSession Class only adds the empty class and the 1:1 linkage to SpiceSession through 2 new private methods added to SpiceSession: spice_session_{get|set}_gtk_session. The following commits will move things which are currently per SpiceDisplay, but which really sho

[Spice-devel] [PATCH spice-gtk 1/3] Fixup some headers so that they include headers the depend up on.

2011-10-04 Thread Hans de Goede
Otherwise they cannot be included unless other headers are included first (and in the right order). Signed-off-by: Hans de Goede --- gtk/spice-channel-cache.h |2 ++ gtk/spice-session-priv.h |1 + 2 files changed, 3 insertions(+), 0 deletions(-) diff --git a/gtk/spice-channel-cache.h b

Re: [Spice-devel] Question on fill_mask() (server/red_worker.c)

2011-10-04 Thread Yaniv Kaul
On 10/04/2011 01:25 PM, Yonit Halperin wrote: On 10/04/2011 01:20 PM, Alon Levy wrote: On Tue, Oct 04, 2011 at 01:00:47PM +0200, Alon Levy wrote: On Tue, Oct 04, 2011 at 12:40:21PM +0200, Yaniv Kaul wrote: Unless I'm misreading the code (which may very well be), the function looks like: if (m

Re: [Spice-devel] Question on fill_mask() (server/red_worker.c)

2011-10-04 Thread Yonit Halperin
On 10/04/2011 01:20 PM, Alon Levy wrote: On Tue, Oct 04, 2011 at 01:00:47PM +0200, Alon Levy wrote: On Tue, Oct 04, 2011 at 12:40:21PM +0200, Yaniv Kaul wrote: Unless I'm misreading the code (which may very well be), the function looks like: if (mask_bitmap&& m) { if (this or that) {

Re: [Spice-devel] Question on fill_mask() (server/red_worker.c)

2011-10-04 Thread Alon Levy
On Tue, Oct 04, 2011 at 01:00:47PM +0200, Alon Levy wrote: > On Tue, Oct 04, 2011 at 12:40:21PM +0200, Yaniv Kaul wrote: > > Unless I'm misreading the code (which may very well be), the > > function looks like: > > > > if (mask_bitmap && m) { > > if (this or that) { > > do X > >

Re: [Spice-devel] Question on fill_mask() (server/red_worker.c)

2011-10-04 Thread Yaniv Kaul
On 10/04/2011 01:00 PM, Alon Levy wrote: On Tue, Oct 04, 2011 at 12:40:21PM +0200, Yaniv Kaul wrote: Unless I'm misreading the code (which may very well be), the function looks like: if (mask_bitmap&& m) { if (this or that) { do X fill_bits(...) } else { fi

Re: [Spice-devel] Question on fill_mask() (server/red_worker.c)

2011-10-04 Thread Alon Levy
On Tue, Oct 04, 2011 at 12:40:21PM +0200, Yaniv Kaul wrote: > Unless I'm misreading the code (which may very well be), the > function looks like: > > if (mask_bitmap && m) { > if (this or that) { > do X > fill_bits(...) > } else { > fill_bits(...) > } > } > > S

[Spice-devel] Question on fill_mask() (server/red_worker.c)

2011-10-04 Thread Yaniv Kaul
Unless I'm misreading the code (which may very well be), the function looks like: if (mask_bitmap && m) { if (this or that) { do X fill_bits(...) } else { fill_bits(...) } } So essentially, if the condition (mask_bitmap && m) is NOT met, we do not fill the b