,
Iskren
From 57f2ef62b7c6c01a4aa1e6944812b97f0ec7b9b4 Mon Sep 17 00:00:00 2001
From: Iskren Chernev iskren.cher...@gmail.com
Date: Fri, 11 Mar 2011 14:19:00 +0200
Subject: [PATCH 1/4] Better cleanup on display creation failure.
---
wayland/wayland-server.c |2 ++
1 files changed, 2 insertions
In my opinion the problem is this:
The code to remove the element from the list is called every time, and the
code to insert it is called only when 'surface'. So in case surface is NULL
the item won't be added, but will be removed next time the function is
entered. Isn't that the case?
I don't
Well, with your patch it doesn't seem to crash. There is also no list
corruption, as far as I could test it :)
Regards,
Iskren
2011/3/13 Kristian Høgsberg k...@bitplanet.net
On Fri, Mar 11, 2011 at 7:32 PM, Iskren Chernev
iskren.cher...@gmail.com wrote:
Hello,
I found a bug and fixed
2011/4/11 Kristian Høgsberg k...@bitplanet.net
On Sun, Apr 10, 2011 at 1:47 PM, Iskren Chernev
iskren.cher...@gmail.com wrote:
Hello,
I think I can do the second point in the TODO file:
The message format has to include information about number of fds
in the message so we can skip
I don't think this lengthy discussion led to any concrete answers, but I do
think that the questions are important and need such answers.
I'll try to summarize the problems that need attention:
1. screen locking
1.1 who is going to implement it: compositor/compositor plugin/app
1.2 inhibit
I can't get one thing out of this discussion.
So you are arguing about client side VS server side decorations,
handling of moves/resizes, maybe even buttons scroll bars etc.
But all wayland does is provide a communication channel that enables
clients to draw in the GPU memory, and then
