Go to file
Pekka Paalanen c0444e3ad6 compositor: force fade-in on start
Weston initialises to faded-out state, which means all outputs are just
black, even if they render fine.

Previously the fade-in was triggered probably by some random input
event, since Weston was not guaranteed to wake up. Especially with the
drm backend, and the usual problem of not having permissions to input
devices, Weston would not fade in at all and appear broken.

Force Weston to fade in right after initialisation. This show that at
least rendering works, if it does not respond to any input.

Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
2012-01-05 16:49:54 +02:00
clients More weston rename fixes 2012-01-03 14:35:49 -05:00
data Rename wayland-compositor to weston 2012-01-03 11:04:04 -05:00
protocol Fix distcheck 2012-01-03 11:04:09 -05:00
shared Use '-' to separate words in file names 2011-12-08 12:44:27 -05:00
src compositor: force fade-in on start 2012-01-05 16:49:54 +02:00
.gitignore Clean up .gitignore files 2010-11-11 20:11:27 -05:00
autogen.sh Update autotools configuration 2010-11-06 21:04:03 -04:00
configure.ac Fix distcheck 2012-01-03 11:04:09 -05:00
Makefile.am Fix distcheck 2012-01-03 11:04:09 -05:00
README Split into a demo repository that holds the demo compositor and clients 2011-02-14 22:13:33 -05:00
weston-desktop-shell.ini More weston rename fixes 2012-01-03 14:35:49 -05:00
weston-tablet-shell.ini More weston rename fixes 2012-01-03 14:35:49 -05:00

Wayland Demos

This repository contains a few demos application for the Wayland
project.  There's a sample compositor that can run on KMS, under X11
or under another Wayland compositor and there's a handful of simple
clients that demonstrate various aspects of Wayland: