On Wed, 22 Nov 2017 10:07:47 +0800
Jonas Ådahl wrote:
> On Wed, Nov 22, 2017 at 03:43:43AM +0200, Jari Vuomajoki wrote:
> > Hi Jasper,
> >
> > Thank you very much for your very clear and comprehensible answer. I
> > understand the challenges you are addressing.
> >
> > I want to build applicati
On Wed, Nov 22, 2017 at 09:17:51AM +0200, Philipp Kerling wrote:
> Hi,
>
> 2017-11-15 (水) の 19:19 +0800 に Jonas Ådahl さんは書きました:
> > Add a copy of xdg-shell unstable v6 to stable/xdg-shell/xdg-
> > shell.xml.
> > Folliwing this commit, it will go through a set of changes, before
> > being declared
Hi,
2017-11-15 (水) の 19:19 +0800 に Jonas Ådahl さんは書きました:
> Add a copy of xdg-shell unstable v6 to stable/xdg-shell/xdg-
> shell.xml.
> Folliwing this commit, it will go through a set of changes, before
> being declared stable.
I have a question here (before declaring it stable) that I hope was not
Looks like the core files have been deleted but the stack traces are
still available. I've attached the logs from coredumpctl for review. I
won't have the ability to run Weston for the next few days, but I
could potentially get you coredumps after that.
Jason
---
Now instead of four in the eights
On Tue, Nov 14, 2017 at 12:23:55PM -0600, Matt Hoosier wrote:
> From: Matt Hoosier
>
> In order to support system compositor instances, it is necessary to
> allow clients' wl_display_connect() to find the compositor's listening
> socket somewhere outside of XDG_RUNTIME_DIR. For a full account, se
On Wed, Nov 22, 2017 at 03:43:43AM +0200, Jari Vuomajoki wrote:
> Hi Jasper,
>
> Thank you very much for your very clear and comprehensible answer. I
> understand the challenges you are addressing.
>
> I want to build applications that can facilitate the screen layout to the
> fullest and still c
Hi Jasper,
Thank you very much for your very clear and comprehensible answer. I
understand the challenges you are addressing.
I want to build applications that can facilitate the screen layout to the
fullest and still collaborate with WM.
I don't really get the "fight" between WM and client. May
Hi,
There's a few reasons that Wayland not to report or allow clients to choose
absolute screen position.
The biggest is that from our experience with X11, it's hard to even
*define* such a space. Laptops plug into external monitors and projectors.
People with differently sized monitors have gaps
Great, thanks!
On Nov 21, 2017 19:02, "Dima Ryazanov" wrote:
> Looks like you're in. Welcome!
>
> On Tue, Nov 21, 2017 at 11:08 PM, Jari Vuomajoki
> wrote:
>
>> Hello!
>>
>> I have now subscribed two times for the list, without getting any
>> confirmation...
>>
>> So am I in or not?
>>
>> Best
Looks like you're in. Welcome!
On Tue, Nov 21, 2017 at 11:08 PM, Jari Vuomajoki
wrote:
> Hello!
>
> I have now subscribed two times for the list, without getting any
> confirmation...
>
> So am I in or not?
>
> Best Wishes,
> Jari Vuomajoki
>
> ___
> w
Hello!
I have been getting to know the Wayland protocol from the client side for
only couple of months... So bare with me if my questions sound immature.
It took a while to get going, the documentation is there and it is
informative enough to build a client. It could be a lot better though or
may
On Tue, Nov 21, 2017 at 10:52:00PM +0800, Jonas Ådahl wrote:
> On Tue, Nov 21, 2017 at 03:45:48PM +0200, Alexandros Frantzis wrote:
> > wl_touch events currently use a 32-bit timestamp with millisecond
> > resolution. In some cases, notably latency measurements, this resolution
> > is too coarse-gr
Hello!
I have now subscribed two times for the list, without getting any
confirmation...
So am I in or not?
Best Wishes,
Jari Vuomajoki
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wa
On Tue, Nov 21, 2017 at 03:45:48PM +0200, Alexandros Frantzis wrote:
> wl_touch events currently use a 32-bit timestamp with millisecond
> resolution. In some cases, notably latency measurements, this resolution
> is too coarse-grained to be useful.
>
> This protocol update adds a wl_touch.timesta
Xwayland is a pretty standard Wayland client, we want to be able to
capture core dumps on crashes.
Yet using "-core" causes any FatalError() to generate a core dump,
meaning that we would get a core file for all Wayland server crashes,
which would generate a lot of false positives.
Instead of usi
wl_touch events currently use a 32-bit timestamp with millisecond
resolution. In some cases, notably latency measurements, this resolution
is too coarse-grained to be useful.
This protocol update adds a wl_touch.timestamp event, which is emitted
just before an up, motion or down touch event. The t
Hello Pekka/Daniel,
As the current review comments are not related with the design of weston-debug
protocol, can we merge this protocol as having the support only for
human-readable log streams. Later the dual-mode framework to support both
human-readable and machine-readable output can be supp
Hi,
Thank you for the patch. It looks good to me.
Reviewed-by: Emre Ucan
Best regards
Emre Ucan
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6937
> -Original Message-
> From: wayland-devel [mailto:wayland-devel-
> boun...@lists.freedesktop.org] On Behalf Of Alexandros Frant
On Tue, 21 Nov 2017 17:08:51 +0900
YoungJun Jo wrote:
> Hi,
>
> The uploaded image was not capture using the camera or mobile phone.
> I captured image using the screenshot program.
> So that's not related display signals or illusion or the human vision.
> The triangle error is shown in the top-
Hi,
If you're worried about FP16 interpolation accuracy (which, as the vendor
states, only gets you 10 bits of accuracy, so only 1024 different values --
definitely not big enough to drive a maximized window at normal desktop
resolutions), you can try using normalized GL_SHORT texture coordinates
On Tue, Nov 21, 2017 at 08:16:09AM +, Arnaud Vrac wrote:
> On Tue, Nov 21, 2017 at 5:54 AM Jonas Ådahl wrote:
>
> > Having a strict requirement on clients obeying the configured window
> > geometry for fullscreen toplevel surfaces might have the side effect of
> > making it harder or impossib
On Wed, Nov 15, 2017 at 01:01:14PM +, David Edmundson wrote:
> Looks good to me!
>
> Reviewed-by: David Edmundson
Thanks, appreciated! Added tag locally so far.
Jonas
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> htt
Hi all,
(sorry for top posting here, I just mean to keep the patch at th end).
I think this patch raise the question of the intended use of FatalError() in
the Xserver.
- as an exit() on error:
port out of range, host not on supported network type, unknown host, etc.
screen init failed,
On Tue, Nov 21, 2017 at 5:54 AM Jonas Ådahl wrote:
> Having a strict requirement on clients obeying the configured window
> geometry for fullscreen toplevel surfaces might have the side effect of
> making it harder or impossible to implement various hardware
> optimizations on certain system conf
Hi,
The uploaded image was not capture using the camera or mobile phone.
I captured image using the screenshot program.
So that's not related display signals or illusion or the human vision.
The triangle error is shown in the top-right area when you see the image
with the original image state of 1
25 matches
Mail list logo
