Hi,
please update it to 1.4 and/or add a simple step by step how
to build the docs yourself (be it in the FAQ region, or in "building
from source").
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/li
Just a reminder on how clocks differ (on LInux) from one another, taken
from here:
http://www.spinics.net/lists/linux-man/msg00973.html
Needless to say, gettimeofday() should be avoided.
CLOCK_REALTIME
- can jump
- can slew
- if ntp is running this clock is always kept close to GMT. even if hardw
Hi,
I think in wayland-client.c the function
wl_display_dispatch_queue_pending(...)
could be simplified
from this:
pthread_mutex_lock(&display->mutex);
if (dispatch_queue(display, queue) == -1)
goto err_unlock;
pthread_mutex_unlock(&display->mutex);
return 0;
err_unlock:
13 at 12:13 PM, Giulio Camuffo wrote:
> 2013/4/16 Jiergir Ogoerg
>
>> Hi,
>> Between application running on X11 apparently there's no standard way to
>> tell if file(s) (their URIs) have been "cut" or "copied" into the
>> clipboard, so you do
Hi,
Between application running on X11 apparently there's no standard way to
tell if file(s) (their URIs) have been "cut" or "copied" into the
clipboard, so you don't know what to do on "Paste", so people invented
(silly) workarounds as explained here [1]:
"Since there is no standard way to copy a
> A lot of useful features require clipboard access and monitoring
> without having a keyboard focus, e.g. clipboard action (klipper[1] and
> some download agents), command line access (IPython's %paste magic).
> This patch sends out selection events to all clients when the
> selection owner change
Hi Kristian,
Your patch calls like 3 times "pthread_cond_wait(..)", shouldn't each of
these calls be in a loop?
>From a book on pthreads:
"You should always wait for a condition variable in a loop, to protect
against errors,
multiprocessor races, and spurious wakeups."
Kind Regards
_
