It seems there is also an issue with the double buffered flow,
namely to make it work cleanly in a the case of a surface
spanning several outputs, those of course not in sync and with
different refresh rates. Better not be in a hurry to do a "page
flip" on a surface which covers several outputs.
O
I don't see why we'd want to remove properties from the output object.
They are still useful for the very common case where a surface is on a
single output only. For example, if a surface is on multiple outputs
with mismatching subpixel layouts, it could turn off subpixel
rendering.
Having clients
Pushed, thanks.
(HTML validated.)
On 03/14, Christopher Michael wrote:
> Hi All :)
>
> I have attached a patch for the Website which updates the EFL build
> instructions. Would greatly appreciate if someone could push this.
>
> Thank You :)
>
> devilhorns
> From ec7eb776364af720afea6bd3ea905
---
weston.ini |2 ++
1 file changed, 2 insertions(+)
diff --git a/weston.ini b/weston.ini
index 98092a1..431bfa9 100644
--- a/weston.ini
+++ b/weston.ini
@@ -9,6 +9,8 @@ locking=true
animation=zoom
#binding-modifier=ctrl
#num-workspaces=6
+#cursor-theme=whiteglass
+#cursor-size=24
#loc
---
man/weston.ini.man |6 ++
1 file changed, 6 insertions(+)
diff --git a/man/weston.ini.man b/man/weston.ini.man
index 7699e35..8dde82c 100644
--- a/man/weston.ini.man
+++ b/man/weston.ini.man
@@ -146,6 +146,12 @@ defines the number of workspaces (unsigned integer). The
user can switch
---
clients/window.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/clients/window.c b/clients/window.c
index 249ba6f..ec3dca8 100644
--- a/clients/window.c
+++ b/clients/window.c
@@ -1095,10 +1095,12 @@ create_cursors(struct display *display)
{
char *config_fil
Hi,
I was looking at why gtk+ clients use a different cursor theme and
size than other (toytoolkit) clients. gtk+ hardcodes the cursor size
to 32 as it has no way to get the preferred (default) size from the
compositor.
I guess one solution would be to have get_default_cursor_theme and
get_defaul
> Your proposal is middle ground: a set of buffers, and some
> heuristics applied on their properties to combine those in the
> compositor space. For simplicity, I dare to think one buffer for
> one output is quite clear cut and easier to deal with.
As a word of clarification, I said " keyed to o
Hi All :)
I have attached a patch for the Website which updates the EFL build
instructions. Would greatly appreciate if someone could push this.
Thank You :)
devilhorns
>From ec7eb776364af720afea6bd3ea90570cbeb8782d Mon Sep 17 00:00:00 2001
From: Chris Michael
Date: Thu, 14 Mar 2013 15:00:26
From: Quentin Glidic
Implement the "bubbles list" style notifications.
Corner anchor, margin and order can be changed in the configuration.
Signed-off-by: Quentin Glidic
---
Rebase on top of current master
src/shell.c | 196 +---
weston
On Mon, Mar 11, 2013 at 3:47 PM, Alex Deucher wrote:
> On Mon, Mar 11, 2013 at 5:39 PM, Scott Moreau wrote:
> >
> >
> > On Mon, Mar 11, 2013 at 12:59 PM, Pekka Paalanen
> > wrote:
> >>
> >> On Sun, 10 Mar 2013 15:53:30 +0100
> >> Hardening wrote:
> >>
> >> > This patch adds a wlrandr extension
On Wed, Mar 13, 2013 at 07:28:17PM +0200, Ran Benita wrote:
> On Mon, Mar 11, 2013 at 12:53:39PM +0100, David Herrmann wrote:
> > The current API doesn't allow the caller to create keymaps from mmap()'ed
> > files. The problem is, xkb_keymap_new_from_string() requires a terminating
> > 0 byte. Howe
On Wed, 13 Mar 2013 19:52:55 +0100
Sylvain BERTRAND wrote:
> The other option would be to ignore those output properties, and
> the compositor would manage something with an output agnostic
> buffer. In that case, we would remove the subpixel property from
> the output to stay consistent (mode i
13 matches
Mail list logo
