Hi again!
Could anyone please help clear up my questions about the compose sequence
syntax?
Thanks in advance!
Mats
2016-01-19 1:16 GMT+01:00 Mats Blakstad :
> I've opened this ticket:
> https://bugs.freedesktop.org/show_bug.cgi?id=93660
>
> I need some feedback to
On Tue, Jan 19, 2016 at 01:16:40AM +0100, Mats Blakstad wrote:
> I've opened this ticket:
> https://bugs.freedesktop.org/show_bug.cgi?id=93660
>
> I need some feedback to be able to upload a final verion!
>
> How should the composer be formatted. Now each composer is added like this:
>
> *
On 3 February 2016 at 15:14, Rui Matos wrote:
> The last cursor frame we commited before the pointer left one of our
> surfaces might not have been shown. In that case we'll have a cursor
> surface frame callback pending which we need to clear so that we can
> continue
Bugzilla: https://bugs.freedesktop.org/92313
---
randr/rrmonitor.c | 6 +++---
randr/rroutput.c | 12
2 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/randr/rrmonitor.c b/randr/rrmonitor.c
index c37dcf8..58041bb 100644
--- a/randr/rrmonitor.c
+++ b/randr/rrmonitor.c
On Feb 5, 2016 12:53 AM, "Rui Matos" wrote:
>
> The last cursor frame we commited before the pointer left one of our
> surfaces might not have been shown. In that case we'll have a cursor
> surface frame callback pending which we need to clear so that we can
> continue
On 04.02.2016 19:05, Lennert Van Alboom wrote:
> Hello. I've got a HP Elitebook 850g1 with hybrid graphics:
>
> $ lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
> Integrated Graphics Controller (rev 0b)
> 03:00.0 VGA compatible controller:
On 03/25/15 11:52 PM, Dominik Muth wrote:
The basic rule "put parantheses around macro parameters" should be
observed where possible. Otherwise code like
ConnectionNumber(foo = bar);
fails to compile. (It obviously passes if ConnectionNumber is a C
function.) There are several other
On 14/01/2016 00:31, Peter Hutterer wrote:
eb36924ead40564325aa56d54a973dc8fb4eae83 removed ChangeWindowProperty from the
server.
Signed-off-by: Peter Hutterer
Reviewed-by: Jon Turney
---
src/dummy_driver.c | 5 +++--
1 file
The last cursor frame we commited before the pointer left one of our
surfaces might not have been shown. In that case we'll have a cursor
surface frame callback pending which we need to clear so that we can
continue submitting new cursor frames.
Signed-off-by: Rui Matos
This should be both more efficient and avoid the file descriptor
exhaustion issue that can happen with shm buffers if we're asked to
realize more cursors than the file descriptor limit.
Signed-off-by: Rui Matos
---
On Sat, Dec 5, 2015 at 1:30 AM, Kristian Høgsberg
On 4 February 2016 at 17:10, Rui Matos wrote:
> This should be both more efficient and avoid the file descriptor
> exhaustion issue that can happen with shm buffers if we're asked to
> realize more cursors than the file descriptor limit.
>
> Signed-off-by: Rui Matos
On Wed, 3 Feb 2016 16:14:09 +0100
Rui Matos wrote:
> The last cursor frame we commited before the pointer left one of our
> surfaces might not have been shown. In that case we'll have a cursor
> surface frame callback pending which we need to clear so that we can
>
12 matches
Mail list logo