- Oct 22, 2012
-
-
Kristian Høgsberg authored
-
Kristian Høgsberg authored
If we have a blank line in the incoming XML documentation, keep that in the emitted doxygen comments.
-
Kristian Høgsberg authored
We were generating headers such as 'Events provided by wl_display events', drop the last 'events'.
-
Kristian Høgsberg authored
-
Kristian Høgsberg authored
We've knocked a few items of the list.
-
- Oct 21, 2012
-
-
Kristian Høgsberg authored
-
- Oct 20, 2012
-
-
Kristian Høgsberg authored
-
Kristian Høgsberg authored
The _* namespace and identifiers with double underscore are reserved by the C standard. That makes __wl_container_of is double plus bad, so lets just call it wl_container_of.
-
Kristian Høgsberg authored
-
- Oct 19, 2012
-
-
Kristian Høgsberg authored
Exporting unprefixed symbols is a pretty bad idea so don't do that. Instea of redefining it WL_ARRAY_LENGTH, we just move the define to our private header. The scanner generates code that uses ARRAY_LENGTH, but we can just make it count the number elements and emit an integer constant instead.
-
Tiago Vignatti authored
Fix https://bugs.freedesktop.org/show_bug.cgi?id=56101 Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>
-
Ander Conselvan de Oliveira authored
-
Ander Conselvan de Oliveira authored
Clarify on what cases each of the dispatching functions may block, what is the main thread and add some real world examples.
-
- Oct 17, 2012
-
-
Ander Conselvan de Oliveira authored
-
John Kåre Alsaker authored
-
- Oct 16, 2012
-
-
Kristian Høgsberg authored
We don't have a use case for this and the actual semantics and synchronization behavior of wl_egl_pixmap were never really well-defined. It also doesn't provide the cross-process buffer sharing that make window systems pixmaps useful in other window systems.
-
John Kåre Alsaker authored
-
John Kåre Alsaker authored
-
John Kåre Alsaker authored
-
John Kåre Alsaker authored
-
Pekka Paalanen authored
Fix few typos in wl_buffer description. Mention backing storage in wl_buffer.destroy. Try to clarify the wl_buffer.release semantics by not explaining what *might* happen. It is important to not suggest, that if release does not come before frame callback, it will not come before attaching a new buffer to the surface. We want to allow the following scenario: The compositor is able to texture from wl_buffers directly, but it also keeps a copy of the surface contents. The copy is updated when the compositor is idle, to avoid the performance hit on wl_surface.attach/commit. When the copy completes some time later, the server sends the release event. If the client has not yet allocated a second buffer (e.g. it updates rarely), it can reuse the old buffer. Reported-by: John Kåre Alsaker <john.kare.alsaker@gmail.com> Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
-
Pekka Paalanen authored
wl_surface.commit itself does not force any repainting unless there is damage, so change the wording to not imply repainting. Reported-by: John Kåre Alsaker <john.kare.alsaker@gmail.com> Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
-
Ander Conselvan de Oliveira authored
-
Ander Conselvan de Oliveira authored
-
Ander Conselvan de Oliveira authored
-
Ander Conselvan de Oliveira authored
It seems a rebase error caused it to end up in the wrong place.
-
Jonas Ådahl authored
Pointer axis events are in the same coordinate space as motion events. Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
-
Kristian Høgsberg authored
-
Kristian Høgsberg authored
publican doesn't seem to be a very well-behaved tool and needs a bit of hacking to work well for both in-tree and out-of-tree builds.
-
- Oct 15, 2012
-
-
Matt Roper authored
Touch grabs allow the compositor to be placed into a mode where touch events temporarily bypass their default behavior and perform other operations. Wayland already supports keyboard and pointer grabs, but was lacking corresponding touch support. The default touch grab handlers here contain the client event delivery code that was previously called directly in weston. Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
-
David Herrmann authored
If any callback or helper function fails with a fatal error, we now set the last_error flag and prevent all further I/O on the wl_display. We wake up all sleeping event-queues and notify the caller that they should shutdown wl_display. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
Kristian Høgsberg authored
This means we're free to close it when we want, which we'll use to wake up the main thread if we hit an error in a different thread.
-
David Herrmann authored
We need access to all event-queues of a single wl_display object. For instance during connection-errors, we need to be able to wake up all event queues. Otherwise, they will be stuck waiting for incoming events. The API user is responsible to keep a wl_display object around until all event-queues that were created on it are destroyed. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
Kristian Høgsberg authored
wl_connection_read() assumes that the caller dispatched all messages before calling it. wl_buffer_put_iov() does only provide enough room so we fill the buffer. So the only case when the buffer overflows, is when a previous read filled up the buffer but we couldn't parse a single message from it. In this case, the client sent a message bigger than our buffer and we should return an error and close the connection. krh: Edited from Davids original patch to just check that the buffer isn't full before we try reading into it. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
Kristian Høgsberg authored
We rely on well-defined unsigned overflow behaviour so let's make the index fields actually unsigned. Signed ints aren't guaranteed to have the behavior we want (could be either ones or twos complement).
-
David Herrmann authored
If we read more FDs than we have room for, we currently leak FDs because we overwrite previous still pending FDs. Instead, we do now close incoming FDs if the buffer is full and return EOVERFLOW. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
David Herrmann authored
Same problem as we had with close_fds(). We cannot rely on the fds_out buffer being filled with less than MAX_FDS_OUT file descriptors. Therefore, write at most MAX_FDS_OUT file-descriptors to the outgoing buffer. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
David Herrmann authored
Same problem as with outgoing FDs. We need to close these on shutdown, otherwise we leak open file descriptors. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
David Herrmann authored
If we push two messages via wl_connection_write() and both messages contain more than MAX_FDS_OUT file-descriptors combined, then wl_connection_flush() will write only MAX_FDS_OUT of them, but close all pending ones, too. Furthermore, close_fds() will copy more FDs out of the buffer than it can hold and cause a buffer overflow. Therefore, we simply pass a maximum limit to close_fds(). During shutdown, we simply close all available FDs. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-
David Herrmann authored
When destroying a wl_connection object, there might still be data in the queue. We would leak open file-descriptors so we must close them. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
-