Hello everyone!I put together my multi-touch UI from bVNC with spice-gtk to create a SPICE client for Android called aSPICE. It has integrated SSH tunneling functionality. The entire project is open source, and is currently based on spice-gtk v.0.19. The source is available here:
https://github.com
Cool, so I'll push it when both protocol & client patches are in.
On 06/09/2013 04:23 PM, Hans de Goede wrote:
ACK :)
Note I plan to write the client side of this, so the actual conversion
code
next week.
On 06/09/2013 03:31 PM, Arnon Gilboa wrote:
rhbz#872252
---
vdagent/vdagent.cpp |
ACK :)
Note I plan to write the client side of this, so the actual conversion code
next week.
On 06/09/2013 03:31 PM, Arnon Gilboa wrote:
rhbz#872252
---
vdagent/vdagent.cpp |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/vdagent/vdagent.cpp b/vdagent/vdagent.cpp
ind
rhbz#872252
---
vdagent/vdagent.cpp |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/vdagent/vdagent.cpp b/vdagent/vdagent.cpp
index a061973..307b7da 100644
--- a/vdagent/vdagent.cpp
+++ b/vdagent/vdagent.cpp
@@ -796,6 +796,7 @@ bool VDAgent::send_announce_capabilities(bool
On 06/09/2013 04:06 PM, Hans de Goede wrote:
Hi,
On 06/09/2013 03:03 PM, agil...@redhat.com wrote:
So conversion is client-only responsibility, while the agent only
needs to advertise its line-ending? seems simpler than conversion in
both sides.
Yep, that is the idea! So the windows agent-si
Hi,
On 06/09/2013 03:03 PM, agil...@redhat.com wrote:
So conversion is client-only responsibility, while the agent only needs to
advertise its line-ending? seems simpler than conversion in both sides.
Yep, that is the idea! So the windows agent-side patch for bug 872252
should be a one liner
So conversion is client-only responsibility, while the agent only needs
to advertise its line-ending? seems simpler than conversion in both sides.
On 06/05/2013 04:18 PM, Hans de Goede wrote:
When copy and pasting between a Linux guest and a Windows client or visa
versa, the line-endings of the
ACK.
On 06/09/2013 01:30 PM, Uri Lublin wrote:
It may happen (not sure how) that a single device appears
twice in the list of USB devices. Only one entry has information
for the currently installed device/driver.
If that happens, currently we just pick the first one, which
may be an invalid ent
It may happen (not sure how) that a single device appears
twice in the list of USB devices. Only one entry has information
for the currently installed device/driver.
If that happens, currently we just pick the first one, which
may be an invalid entry that says a nont-WinUSB (e.g. USBSTOR)
is the d
