GitLab

This way we add support for non-ascii chars

BUG: 340764

Jens Dagerbo authored Nov 09, 2014 and Albert Vaca Cintora committed Nov 09, 2014

No longer keeping the entire file in RAM while uploading

Bug: 338951

BUG: 338662

The build system cannot guess that a new build dependency was added.

I've also removed modifiers like Shift and Ctrl by now.

LibFakeKey is now a dependency of this plugin, as it allows us to send UTF
characters as X11 keys in a simple and convenient way. Internally it uses a
convention in Xlib, that allows to pass UTF characters as keycodes just by
adding 0x01000000 to the keycode number.

CCMAIL: saiarcot895@gmail.com

Saikrishna Arcot authored Aug 01, 2014 and Albert Vaca Cintora committed Aug 14, 2014

This patch gets the keyboard entries from the Android client and passes
along the keycode.

REVIEW: 119254

We already have a refresh button on Android.

Probably it was not detecting connections to a wired interface either,
this should do the trick but it's a bit weird having to connect to
QNetworkConfigurationManager::configurationAdded() to know about that.

Only lets the plugins that support something offered on the other end or
that offer something supported on the other end. If we don't have
information about the other device, we enable everything like we used to.

Also refactors a bit the plugin loader, to be able to provide information
step by step.

Currently it works, but we need support for capabilities at least on
Android to start taking good advantage of it.

REVIEW: 118820
CCMAIL: kdeconnect@kde.org

David Suárez authored Jul 07, 2014 and Aleix Pol Gonzalez committed Jul 07, 2014

TestSocketLineReader: Ensure we provide a more appropiate message if we fail trying to open a connection to the client

A litle irrelevant change :)

BTW, I'm encounter this test error on Debian kfreebsd i386:
  https://buildd.debian.org/status/fetch.php?pkg=kdeconnect&arch=kfreebsd-i386&ver=0.7-1&stamp=1404242653

Maybe someone have a clue on what is happening here :)

REVIEW: 119091