John Kåre Alsaker wrote:
On Thu, Dec 13, 2012 at 11:47 PM, Bill Spitzak wrote:
I see no reason for extra objects. What I would do is add a "parent" to the
normal surface. If it is NULL then it is a "main" surface. If it points at
another surface then it is a subsurface or a floating window. T
On Thu, Dec 13, 2012 at 11:47 PM, Bill Spitzak wrote:
> I see no reason for extra objects. What I would do is add a "parent" to the
> normal surface. If it is NULL then it is a "main" surface. If it points at
> another surface then it is a subsurface or a floating window. The "parent"
> can be cha
Tiago Vignatti wrote:
About the availability of it to regular Wayland clients, I agree, it's a
problem. Bill Spitzak pointed this out on the previous set. It sets a
bad example because it exposes global position to all regular clients
and we don't want this.
Actually I prefer this. I think i
I see no reason for extra objects. What I would do is add a "parent" to
the normal surface. If it is NULL then it is a "main" surface. If it
points at another surface then it is a subsurface or a floating window.
The "parent" can be changed arbitrarily. We must be able to change an
existing sur
On Thu, Dec 13, 2012 at 10:01:25AM +0200, Pekka Paalanen wrote:
Oh, yeah, that's pretty simple. Thanks.
Kristian
> Signed-off-by: Pekka Paalanen
> ---
> tests/Makefile.am |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/tests/Makefile.am b/tests/Makefile.am
> i
On Thu, Dec 13, 2012 at 04:07:44PM +0100, John Kåre Alsaker wrote:
> I added buffered commit_surface in wl_surface_group, which allows
> clients to atomically update the surfaces of their choice. This way we
> don't have to change wl_surface.commit. We can also update the main or
> parent surface a
On 12/13/2012 05:38 AM, Pekka Paalanen wrote:
On Wed, 12 Dec 2012 13:26:33 -0200
Tiago Vignatti wrote:
X11 apps use global coordinates most of the time for window placement and the
current approach we have, where transient windows is placed parent relative,
is not sufficient. IOW we can't us
I added buffered commit_surface in wl_surface_group, which allows
clients to atomically update the surfaces of their choice. This way we
don't have to change wl_surface.commit. We can also update the main or
parent surface and subsurfaces independently.
Hi John,
On Thu, 13 Dec 2012 14:51:17 +0100
John Kåre Alsaker wrote:
> Here is my "subsurface" proposal. I don't like video sinks (or other
> things) running on an independent framerate. I don't want to maintain
> more state in the compositor side for them or have increased
> complexity in the
Here is my "subsurface" proposal. I don't like video sinks (or other
things) running on an independent framerate. I don't want to maintain
more state in the compositor side for them or have increased
complexity in the protocol. They are inefficient and can be solved by
a number of other ways. In th
On Wed, 12 Dec 2012 14:22:49 +
Daniel Stone wrote:
> Hi,
>
> On 6 December 2012 01:32, Pekka Paalanen wrote:
>
> > Clipping
> >
> > The term sub-surface sounds like a sub-window, which may cause one to
> > think, that it will be clipped to the parent surface area. I do not
> > think we sho
On Wed, 12 Dec 2012 10:58:31 -0500
Kristian Høgsberg wrote:
> On Wed, Dec 12, 2012 at 02:44:52PM +0200, Pekka Paalanen wrote:
> > On Wed, 12 Dec 2012 14:26:38 +0200
> > Pekka Paalanen wrote:
> >
> > > This cleans up the 'make check' output considerably. When all goes well,
> > > you will only s
Signed-off-by: Pekka Paalanen
---
tests/Makefile.am |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/tests/Makefile.am b/tests/Makefile.am
index 05d5d00..7d6b6e0 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -12,6 +12,9 @@ weston_tests =
13 matches
Mail list logo
