Hi,
On 18 March 2013 02:55, Sylvain BERTRAND wrote:
> Another though which targets sub-surface interfaces: are the
> hardware overlays for YUV buffers that more energy efficient than
> GPU scaling/color space conversion since most the energy would be
> burned into the video decoding anyway?
Ye
Hi,
On 18 March 2013 01:47, Yichao Yu wrote:
> On Sun, Mar 17, 2013 at 8:51 PM, Scott Moreau wrote:>
> by wayland developers that each toolkit should implement this feature
> > if they would like to have it. My position is that the key repeat
>
> And the decision was all toolkits/programs writt
Hi again,
I put some more thoughts in those issues.
A client knows on which outputs its surfaces span over. Then the
client is in charge of configuring its rendering to find the best
trade off, but with one buffer. If the surface was entered on 2
outputs with really different DPIs... well it shou
On Sun, Mar 17, 2013 at 7:47 PM, Yichao Yu wrote:
> Hi Scott,
>
> On Sun, Mar 17, 2013 at 8:51 PM, Scott Moreau wrote:
>> On Sun, Mar 17, 2013 at 5:36 PM, Yichao Yu wrote:
>>> Hi,
>>>
>>> Seems that weston uses a client side keyboard auto-repeat that is
>>> HARD-CODED in `window.c` and I haven't
Hi Jason,
Thanks for your reply.
On Sun, Mar 17, 2013 at 7:24 PM, Jason Ekstrand wrote:
> On Fri, Mar 8, 2013 at 4:39 PM, Scott Moreau wrote:
>>
>>
>> On Fri, Mar 8, 2013 at 3:28 PM, Bill Spitzak wrote:
>>>
>>> Scott Moreau wrote:
>>>
"Further, the term minimize is relatively subjective a
On Sun, Mar 17, 2013 at 9:21 PM, wrote:
> (Client Side Decorations.)
>
> 08:19PM < krh> in other news, the csd branch of gtk+ was merged today
> 08:20PM < soreau> They have min/max buttons hidden by default
> 08:20PM < krh> that's how the theme is
> 08:21PM < soreau> krh: How do you change the th
Hi Scott,
On Sun, Mar 17, 2013 at 8:51 PM, Scott Moreau wrote:
> On Sun, Mar 17, 2013 at 5:36 PM, Yichao Yu wrote:
>> Hi,
>>
>> Seems that weston uses a client side keyboard auto-repeat that is
>> HARD-CODED in `window.c` and I haven't seen anywhere in wayland's
>> mentioning how this should be
On Fri, Mar 8, 2013 at 4:39 PM, Scott Moreau wrote:
>
>
> On Fri, Mar 8, 2013 at 3:28 PM, Bill Spitzak wrote:
>>
>> Scott Moreau wrote:
>>
>>> "Further, the term minimize is relatively subjective and defined by the
>>> implementation. Clients should not expect that minimized means the
>>> surface
(Client Side Decorations.)
08:19PM < krh> in other news, the csd branch of gtk+ was merged today
08:20PM < soreau> They have min/max buttons hidden by default
08:20PM < krh> that's how the theme is
08:21PM < soreau> krh: How do you change the theme in wayland without
recompiling?
On Sun, Mar 17, 2013 at 5:36 PM, Yichao Yu wrote:
> Hi,
>
> Seems that weston uses a client side keyboard auto-repeat that is
> HARD-CODED in `window.c` and I haven't seen anywhere in wayland's
> mentioning how this should be done in wayland. There doesn't seem to
> be a place where the client can
On Sun, Mar 17, 2013 at 7:30 PM, Hardening wrote:
> On 17/03/2013 23:59, Sylvain BERTRAND wrote:
>> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote:
>>> This patch adds a shutdow event so that clients can be notified
>>> when the compositor is about to exit (and potentially kill its
>>>
Hi,
Seems that weston uses a client side keyboard auto-repeat that is
HARD-CODED in `window.c` and I haven't seen anywhere in wayland's
mentioning how this should be done in wayland. There doesn't seem to
be a place where the client can get a recommended repeat delay and
frequency from the server
On 17/03/2013 23:59, Sylvain BERTRAND wrote:
> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote:
>> This patch adds a shutdow event so that clients can be notified
>> when the compositor is about to exit (and potentially kill its
>> child processes).
>> This patch is based on gh next.
>
On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote:
> This patch adds a shutdow event so that clients can be notified
> when the compositor is about to exit (and potentially kill its
> child processes).
> This patch is based on gh next.
Is the socket disconnect not enough information for t
Wouldn't be better to use struct wl_notification_daemon pointers
instead of struct desktop_shell?
2013/3/14 Quentin Glidic :
> From: Quentin Glidic
>
> Implement the "bubbles list" style notifications.
> Corner anchor, margin and order can be changed in the configuration.
>
> Signed-off-by: Quent
This patch adds a shutdow event so that clients can be notified
when the compositor is about to exit (and potentially kill its
child processes).
This patch is based on gh next.
---
protocol/wayland.xml |7 +++
src/wayland-client.c | 26 +-
src/wayland-client.h |
On Fri, Mar 15, 2013 at 07:33:39PM -0500, Jason Ekstrand wrote:
> ---
> This patch should actually go at the begining of the series before 1/6. I
> accidentally forgot to include it and didn't notice until someone tried to
> apply the series.
Thanks. I squashed the commit into Jonas' connection.
On Fri, Mar 08, 2013 at 06:44:16PM +0100, Jonas Ådahl wrote:
> This commit adds a flags parameter to wl_closure_invoke(). The so far
> added flags are ment to specify if the invokation is client side or
> server side. When on the server side, closure arguments of type 'new_id'
> should be invoked a
On Thu, Mar 07, 2013 at 11:32:39PM +0100, Jonas Ådahl wrote:
> The llvm static analyzer tool reported "Use of memory after it is freed"
> in dispatch_event() because the proxy is used after being freed if the
> reference count reaches zero without the destroyed flag being set. This
> would never ha
On Sun, Mar 17, 2013 at 11:47 AM, John Kåre Alsaker
wrote:
> I believe this is the wrong approach. I'd rather see some generic way
> to share any wl_object between clients securely. I don't see a
> transfer of ownership of your handle which means any client and get
> access to it.
There is no par
I believe this is the wrong approach. I'd rather see some generic way
to share any wl_object between clients securely. I don't see a
transfer of ownership of your handle which means any client and get
access to it.
I'd rather have something like this:
One connection uses
I suggest we apply all of them except the last 4 which add dispatcher
support. That allows us to slowly fix the other projects with the new
API.
On Sat, Mar 16, 2013 at 9:25 PM, Scott Moreau wrote:
> Hi Jason,
>
> I appreciate your work here. These patches can potentially lower the
> entry barrie
On Sat, Mar 16, 2013 at 1:24 PM, Martin Minarik
wrote:
> Track mouse button values. When the kernel drops, don't
> send notify again about a button, that's already pressed or released.
Hi Martin,
Not sure that the approach used in the patch is the proper fix to this
issue. It seems that what is
A logical surface is a special kind of surface that never gets its own
buffer attached, or opaque region set etc. It is obtained by using a
surface handle that can be shared in some way between clients. A handle
is a server wide unique identifier retrieved from the server given a
real surface. Curr
24 matches
Mail list logo
