On Fri, Oct 16, 2015 at 06:58:32PM -0700, Bill Spitzak wrote:
> On Mon, Oct 12, 2015 at 10:01 PM, Peter Hutterer
> wrote:
>
> At least based on this example, I think this is fixing the wrong problem.
> > knowing which device sends a key is fairly meaningless unless you have
> > direct access to t
On Mon, Oct 12, 2015 at 10:01 PM, Peter Hutterer
wrote:
At least based on this example, I think this is fixing the wrong problem.
> knowing which device sends a key is fairly meaningless unless you have
> direct access to the devices anyway (which you probably don't, at least not
> in the default
I wish to formally state that I very seriously believe this proposal is
wrong. The action must be decided by the destination client, not the way
this is trying to do it.
On Fri, Oct 16, 2015 at 8:59 AM, Mike Blumenkrantz
wrote:
> On Fri, 16 Oct 2015 16:52:44 +0100
> Daniel Stone wrote:
>
> > Hi
On Thu, Oct 1, 2015 at 12:57 PM, Carlos Garnacho wrote:
> On Thu, Oct 1, 2015 at 8:48 PM, Bill Spitzak wrote:
> >
> >
> > On Wed, Sep 30, 2015 at 1:45 PM, Carlos Garnacho
> wrote:
> >>
> >>
> >> - wl_data_source.drop_performed: Happens when the operation has been
> >> physically finished (eg.
On 10/15/2015 01:51 AM, Pekka Paalanen wrote:
> I think it's better to land this stuff in pieces than massage a
> humongous replace-the-world patch series, if we can tell the pieces are
> going in the right direction. The bits here are mostly just following
> the existing weston-test-client-helper.
On Fri, Oct 16, 2015 at 12:10:57PM +0300, Pekka Paalanen wrote:
> On Fri, 16 Oct 2015 10:27:56 +0200
> Hardening wrote:
>
> > Le 16/10/2015 03:28, Bryce Harrington a écrit :
> > > On Tue, Oct 13, 2015 at 01:59:13PM +0200, Joaquim Duran wrote:
> > >> Hello,
> > >>
> > >> When configuring the Westo
[and again, with the actual CC this time ...]
On Friday, 16 October 2015, Daniel Stone wrote:
> Hi,
>
> On Wednesday, 30 September 2015, Carlos Garnacho > wrote:
>
>> Currently, there's no means for the DnD origin to know whether the
>> destination is actually finished with the DnD transaction,
On Fri, 16 Oct 2015 16:53:28 +0100
Daniel Stone wrote:
> Hi,
>
> On Wednesday, 30 September 2015, Carlos Garnacho
> wrote:
>
> > Currently, there's no means for the DnD origin to know whether the
> > destination is actually finished with the DnD transaction, short of
> > finalizing it after th
On Fri, 16 Oct 2015 16:52:44 +0100
Daniel Stone wrote:
> Hi,
>
> On Wednesday, 30 September 2015, Carlos Garnacho
> wrote:
>
> > These 2 requests have been added:
> >
> > - wl_data_source.set_actions: Notifies the compositor of the
> > available actions on the data source.
> > - wl_data_offer.
[and again, with the actual CC this time ...]
On Friday, 16 October 2015, Daniel Stone wrote:
> Hi,
>
> On Wednesday, 30 September 2015, Carlos Garnacho > wrote:
>
>> Currently, there's no means for the DnD origin to know whether the
>> destination is actually finished with the DnD transaction,
Hi,
On Wednesday, 30 September 2015, Carlos Garnacho wrote:
> Currently, there's no means for the DnD origin to know whether the
> destination is actually finished with the DnD transaction, short of
> finalizing it after the first transfer finishes, or leaking it forever.
>
> But this poses othe
Hi,
On Wednesday, 30 September 2015, Carlos Garnacho wrote:
> These 2 requests have been added:
>
> - wl_data_source.set_actions: Notifies the compositor of the available
> actions on the data source.
> - wl_data_offer.set_actions: Notifies the compositor of the available
> actions on the de
Le 16/10/2015 11:53, David FORT a écrit :
> This patch implements inert objects for wl_keyboard, wl_pointer and wl_touch.
> The target case is when the server has just send a capability event about a
> disappearing object, and the client binds the corresponding object. We bind an
> inert object: an
On 16/10/15 09:04 AM, Giulio Camuffo wrote:
> 2015-10-16 16:46 GMT+03:00 Pekka Paalanen :
>> On Sun, 4 Oct 2015 13:46:03 +0300
>> Giulio Camuffo wrote:
>>
>>> 2015-06-26 19:34 GMT+03:00 Derek Foreman :
From irc:
it creates a wl_buffer object in a way that no client can ever
ac
2015-10-16 16:46 GMT+03:00 Pekka Paalanen :
> On Sun, 4 Oct 2015 13:46:03 +0300
> Giulio Camuffo wrote:
>
>> 2015-06-26 19:34 GMT+03:00 Derek Foreman :
>> > From irc:
>> > it creates a wl_buffer object in a way that no client can ever
>> > access the storage.
>> >
>> > So, let's replace it w
On Sun, 4 Oct 2015 13:46:03 +0300
Giulio Camuffo wrote:
> 2015-06-26 19:34 GMT+03:00 Derek Foreman :
> > From irc:
> > it creates a wl_buffer object in a way that no client can ever
> > access the storage.
> >
> > So, let's replace it with abort(); and mark it with WL_DEPRECATED
> > in the
On Mon, 5 Oct 2015 13:12:12 -0500
Derek Foreman wrote:
> Sometimes the compositor wants to make sure a shm pool doesn't disappear
> out from under it.
>
> For example, in Enlightenment, rendering happens in a separate thread
> while the main thread can still dispatch events. If a client is des
Le 16/10/2015 11:53, David FORT a écrit :
> This patch implements inert objects for wl_keyboard, wl_pointer and wl_touch.
> The target case is when the server has just send a capability event about a
> disappearing object, and the client binds the corresponding object. We bind an
> inert object: an
This patch implements inert objects for wl_keyboard, wl_pointer and wl_touch.
The target case is when the server has just send a capability event about a
disappearing object, and the client binds the corresponding object. We bind an
inert object: an object does nothing when it is requested. If the
The database of keymaps are not included in xkbcommon library, you
should download from
http://www.freedesktop.org/wiki/Software/XKeyboardConfig and then just
install all keymaps that you need.
Joaquim Duran
2015-10-16 11:31 GMT+02:00 Arnaud Vrac :
> On Fri, Oct 16, 2015 at 11:10 AM, Pekka Paala
On Fri, Oct 16, 2015 at 11:10 AM, Pekka Paalanen
wrote:
> On Fri, 16 Oct 2015 10:27:56 +0200
> Hardening wrote:
>
> > Le 16/10/2015 03:28, Bryce Harrington a écrit :
> > > On Tue, Oct 13, 2015 at 01:59:13PM +0200, Joaquim Duran wrote:
> > >> Hello,
> > >>
> > >> When configuring the Weston proje
On Fri, 16 Oct 2015 10:27:56 +0200
Hardening wrote:
> Le 16/10/2015 03:28, Bryce Harrington a écrit :
> > On Tue, Oct 13, 2015 at 01:59:13PM +0200, Joaquim Duran wrote:
> >> Hello,
> >>
> >> When configuring the Weston project, it is possible to disable (don't
> >> include) the library libxkbcomm
On Fri, 16 Oct 2015 12:29:11 +1000
Peter Hutterer wrote:
> On Fri, Oct 09, 2015 at 01:16:49PM +0200, Nils Chr. Brause wrote:
> > Hi,
> >
> > Reviewed-by: Nils Christopher Brause
> >
> > I ran distcheck and it worked. :)
>
> a bit late, but I would like to register my disagreement with this pa
Hi, everyone
I have built Tizen-IVI image(tizen-ivi-image-dev) with single seat using
yocto and run it on MCIMX6Q-SDP:
tizen-distro : tizen-ivi branchmeta-fsl-arm/meta-fsl-arm-extra: dizzy
(kernel is upgraded to 3.14.28, imx-gpu-viv is upgraded to 5.0.11)
Then I configed boot par
Le 16/10/2015 10:34, Joaquim Duran a écrit :
> Disable xkbcommon library could be useful in devices based on
> touchscreen, like smartphones, but if you have USB connectors, you
> could connect an external keyboard. if xkbcommon is a small library,
> just change the documentation.
>
> Joaquim Dura
Disable xkbcommon library could be useful in devices based on
touchscreen, like smartphones, but if you have USB connectors, you
could connect an external keyboard. if xkbcommon is a small library,
just change the documentation.
Joaquim Duran
2015-10-16 10:27 GMT+02:00 Hardening :
> Le 16/10/2015
Le 16/10/2015 03:28, Bryce Harrington a écrit :
> On Tue, Oct 13, 2015 at 01:59:13PM +0200, Joaquim Duran wrote:
>> Hello,
>>
>> When configuring the Weston project, it is possible to disable (don't
>> include) the library libxkbcommon. To compile Weston successfully,
>> even if the option --disabl
27 matches
Mail list logo
