Hi,
I thought I would try to push this [1] protocol along, as it's what
would be needed for wayland client gamepad input. There is still no
client-side "libgamepadinput", so clients are on their own when it comes
to handling these devices.
Here is a basic proof-of-concept implementation for
On 2018-12-10 3:24 PM, Jonas Ådahl wrote:
> This reason comes up everytime D-Bus is mentioned, and I think it's
> somewhat counter productive; I don't think this is a problem clients
> should try to avoid so hard. D-Bus is more or less the universal IPC on
> Linux, is used quite extensively to
On Mon, Dec 10, 2018 at 02:10:30PM +, Simon Ser wrote:
> On Monday, December 10, 2018 2:51 PM, Jonas Ådahl wrote:
> > There is an alternative more generic solution to this problem, and all
> > other related to what XSettings did in the past. If we'd end up
> > introducing a protocol like
On Monday, December 10, 2018 2:51 PM, Jonas Ådahl wrote:
> There is an alternative more generic solution to this problem, and all
> other related to what XSettings did in the past. If we'd end up
> introducing a protocol like this, we might end up with many tiny
> protocols for things previously
There is an alternative more generic solution to this problem, and all
other related to what XSettings did in the past. If we'd end up
introducing a protocol like this, we might end up with many tiny
protocols for things previously covered by XSettings. Cursor things,
font things, and what not.
On Sun, 9 Dec 2018 16:07:22 +0100
Peter Bašista wrote:
> Hi,
>
> Weston does not seem to perform any output scaling unless an explicit and
> correct output name is given.
Hi,
yes, that is correct. A correct output name must be given.
> At least in my case, it was *not* sufficient
> to add
