On Tue, May 31, 2016 at 10:18:58AM +0200, Hans de Goede wrote:
> Hi,
>
> On 31-05-16 02:16, Peter Hutterer wrote:
> > No need to handle events properly in the edge scroll state machine when it's
> > not enabled. Just set any beginning touch to state AREA and move on. The
> > rest
> > of the code
Welcome to the official release of Weston 1.11, here's a run-down of
some of the main changes since the last stable release.
== libweston ==
A concerted effort to push the libweston development along reworked how
backends are configured to permit them to be initialized independent of
Weston's ma
This is the official release of Wayland 1.11. Here's a brief synopsis
of some of the key enhancements provided by this update.
Proxy wrappers were introduced, which help avoid race conditions in
multi-threaded clients. A new "proxy wrapper" API is added for the
client to use when sending request
Quite a few bugs are caused by touchpad ranges being out of whack. If we get
input events significantly outside the expected range (5% width/height as
error margin) print a warning to the log.
And add a new doc page to explain what is happening and how to fix it.
Signed-off-by: Peter Hutterer
--
Hello Derek,
Maybe I fail to explain my point of view:
I propose to have only one state array, I also propose that client
provide hints about which optional state he support. This is somehow
similar to EWMH - _NET_WM_STATE and EWMH - _NET_WM_ALLOWED_ACTIONS
respectively.
my arguments are:
- sta
On 31/05/16 02:31 PM, Benoit Gschwind wrote:
> Hello mike,
>
> Thank for your clarification, I try to summarize the issue/need:
>
> A compositor may want to draw a client without the shadow. In particular
> if the window is integrated to a GUI component, I can imagine tilling.
Tiling seems only
Hello mike,
Thank for your clarification, I try to summarize the issue/need:
A compositor may want to draw a client without the shadow. In particular
if the window is integrated to a GUI component, I can imagine tilling.
Taking your issue, the drawing state look very similar to the state
flags.
After a long weekend of not reading mails, I've read some mails; I'll try
to make comments to everything in this reply.
On Tue, May 31, 2016 at 7:38 AM Olivier Fourdan wrote:
> Hey
>
> - Original Message -
> > On Tue, May 31, 2016 at 05:24:35AM -0400, Olivier Fourdan wrote:
> > > [...]
>
On May 30, 2016, at 4:41 AM, Jan Arne Petersen wrote:
>
> There were some shortcomings in the first version of the protocol which
> makes it not really useful in real world applications. It is not really
> possible to fix them in a compatible way so introduce a new v2 of the
> protocol.
>
> Fixe
On Tue, May 31, 2016 at 02:49:38PM +0100, adlo wrote:
>
> > On 20 May 2016, at 08:50, Pekka Paalanen wrote:
> >
> > You would design a new protocol extension private to Weston, with which
> > you deliver to your client the handles for top-level windows as they
> > come and go.
> >
>
> This sho
> On 20 May 2016, at 08:50, Pekka Paalanen wrote:
>
> You would design a new protocol extension private to Weston, with which
> you deliver to your client the handles for top-level windows as they
> come and go.
>
This should probably be a separate protocol from the preview protocol. Is it
po
Note: Reconstructed response from mailing list digest, apologies if
this doesn't thread correctly.
In-Reply-To: 1458404075-1811-1-git-send-email-giulio.camu...@kdab.com
X-Patchwork-Id: 77583
On 19 Mar 2016 18:14:35 +0200, Giulio Camuffo wrote:
The wl_proxy_add_listener function is ill-na
On Tue, 31 May 2016 09:13:13 +
"Potrola, MateuszX" wrote:
> Hi,
>
> > Even more so, because as far as I can see, to actually see the badly sized
> > surface
> > you have to do this in ivi-layout API:
> > 1. add the surface to a layer
> > 2. set visibility true
> > 3. commit_changes
> > 4. s
On Thu, 26 May 2016 13:52:58 +0100
adlo wrote:
> > On 24 May 2016, at 16:06, Pekka Paalanen wrote:
> >
> > The "private to weston" also means it should be a privileged interface:
> > arbitrary clients must not be able to use it, as it's none of their
> > concern and could be a security concern.
> On 11 May 2016, at 09:07, Pekka Paalanen wrote:
>
> If some sort of protocol would be needed, then you have to figure out
> how to not make it a gaping security breach
>
What about Wayland Security Modules (libwsm)? In what ways does this fail to
address the security issues with privileged
Hey
- Original Message -
> On Tue, May 31, 2016 at 05:24:35AM -0400, Olivier Fourdan wrote:
> > [...]
> > If we considered and dismissed them, fine.
>
> They are not "actively" considered in this patch, but as I mentioned
> earlier, I think tiling states can later be added to the window s
On Tue, May 31, 2016 at 05:24:35AM -0400, Olivier Fourdan wrote:
> Hey
>
> Just to make it clear, as a foreword to my comments inline below, I am not
> against the patch, far from it, I just wanted to make sure we considered edge
> values instead of only "no shadow", and we also considered other
On Tue, May 31, 2016 at 11:16:51AM +0200, Benoit Gschwind wrote:
>
>
> On 31/05/2016 10:53, Jonas Ådahl wrote:
> > On Tue, May 31, 2016 at 10:31:28AM +0200, Benoit Gschwind wrote:
> >> Hello Jonas, Mike and Olivier,
> >>
> >> On 30/05/2016 15:09, Olivier Fourdan wrote:
> >>> Hi Jonas,
> >>>
> >>>
Hello,
Just a reply to EWMH/MOTIF comments,
EWMH semantic is the path already started within xdg, as far as remember
v6 have toplevel, popup and tooltips surfaces, and will probably have
many more in the future.
That why we need a description of the issue we trying to solve. I can
assume that th
Hey
Just to make it clear, as a foreword to my comments inline below, I am not
against the patch, far from it, I just wanted to make sure we considered edge
values instead of only "no shadow", and we also considered other draw states.
If we considered and dismissed them, fine.
For reference, t
On 31/05/2016 10:53, Jonas Ådahl wrote:
> On Tue, May 31, 2016 at 10:31:28AM +0200, Benoit Gschwind wrote:
>> Hello Jonas, Mike and Olivier,
>>
>> On 30/05/2016 15:09, Olivier Fourdan wrote:
>>> Hi Jonas,
>>>
>>> - Original Message -
On Mon, May 30, 2016 at 05:01:58AM -0400, Olivier
Hi,
> Even more so, because as far as I can see, to actually see the badly sized
> surface
> you have to do this in ivi-layout API:
> 1. add the surface to a layer
> 2. set visibility true
> 3. commit_changes
> 4. set source rectangle
> 5. commit_changes
>
> At step 3, the surface will be shown.
On Tue, May 31, 2016 at 10:31:28AM +0200, Benoit Gschwind wrote:
> Hello Jonas, Mike and Olivier,
>
> On 30/05/2016 15:09, Olivier Fourdan wrote:
> > Hi Jonas,
> >
> > - Original Message -
> >> On Mon, May 30, 2016 at 05:01:58AM -0400, Olivier Fourdan wrote:
> >>>
> >>> Do we really want
Hello Jonas, Mike and Olivier,
On 30/05/2016 15:09, Olivier Fourdan wrote:
> Hi Jonas,
>
> - Original Message -
>> On Mon, May 30, 2016 at 05:01:58AM -0400, Olivier Fourdan wrote:
>>>
>>> Do we really want reserved ranges here?
>>>
>>> Some people reckon having (undocumented) reserved ran
Hi,
On 31-05-16 02:16, Peter Hutterer wrote:
No need to handle events properly in the edge scroll state machine when it's
not enabled. Just set any beginning touch to state AREA and move on. The rest
of the code guarantees neutral state when edge scrolling is enabled or
disabled.
This reduces t
On Mon, 30 May 2016 13:10:42 +0200
Miguel Angel Vico wrote:
> Hi all,
>
> A few days ago, I had a little chat over IRC with Pekka about addition
> of proxy objects destruction callbacks to the wayland client protocol.
>
>
> Summing up, we recently ran into some applications where native object
Hello Mike and Jonas,
I wonder why ?
I do not saying you proposal is useless, but any proposal should solve
an issue or add a feature to be discussed. In both case, I think a
proposal must provide an explanation of why this proposal.
This may be obvious for you but it might be not so obvious. An
27 matches
Mail list logo
