https://bugs.kde.org/show_bug.cgi?id=370919
Albert Vaca changed:
What|Removed |Added
CC||ci3...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=370919
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=370919
azr...@googlemail.com changed:
What|Removed |Added
CC||azr...@googlemail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=370919
Christoph Feck changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=370919
Aleix Pol changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=370919
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #12 from Holger Kaelberer ---
(In reply to OlafLostViking from comment #10)
> For a functionality that lets me control the phone on my desktop (the best
> would be just "mirror" one Android app into a window on my
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #11 from Holger Kaelberer ---
kde: https://git.reviewboard.kde.org/r/129727/
Android: https://git.reviewboard.kde.org/r/129728/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #10 from OlafLostViking ---
I'm happy to read about your plans - thank you!
For a functionality that lets me control the phone on my desktop (the best
would be just "mirror" one Android app into a window on
https://bugs.kde.org/show_bug.cgi?id=370919
OlafLostViking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #9 from Albert Vaca ---
Awesome :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #7 from Albert Vaca ---
mobile-to-desktop and desktop-to-mobile should be in different plugins (like in
the case of notifications), because they are not "symmetrical": a device can
support only receiving keys but not
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #6 from Holger Kaelberer ---
Thanks for your feedback.
(In reply to Albert Vaca from comment #3)
> I think this is a needed addition to kdeconnect. About the format of the
> packets, ideally it should be the same as
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #5 from Albert Vaca ---
Oh, and about the UI... I'm not sure what's the best way to present it to the
user on the desktop, but the text field in the plasmoid probably works. About
the phone side, registering it as a
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #4 from Albert Vaca ---
[continues previous comment] makes sense for capabilities to be able to disable
the part that is actually not available without disabling other features that
do work (that's what happens if we
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #3 from Albert Vaca ---
I think this is a needed addition to kdeconnect. About the format of the
packets, ideally it should be the same as the one used for desktop to phone
communication. This way, it will work desktop
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #2 from Holger Kaelberer ---
(In reply to Holger Kaelberer from comment #1)
> * On-the-wire format:
Oups, I just realized that I forgot doing the most obvious thing: look at how
keys are serialized in the mousepad
https://bugs.kde.org/show_bug.cgi?id=370919
--- Comment #1 from Holger Kaelberer ---
I've got an experimental implementation of an InputMethod on Android to inject
key-events from desktop-to-mobile. After some testing and improvements it seems
to work pretty well for
https://bugs.kde.org/show_bug.cgi?id=370919
Holger Kaelberer changed:
What|Removed |Added
CC||aleix...@gmail.com,
19 matches
Mail list logo