Em quinta-feira, 14 de julho de 2016, às 01:38:13 PDT, Emmanuel Gil Peyrot
escreveu:
> > Out of curiosity: why are you compiling C sources as C++?
> >
> > Is that the Arduino compiler?
>
> I wasn’t, I just noticed this leftover from a previous copy (likely the
> file creation), and just fixed
> -#ifdef __cplusplus
> -}
> -#endif
Out of curiosity: why are you compiling C sources as C++?
Is that the Arduino compiler?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
On Wed, Jul 13, 2016 at 05:13:24PM -0700, Thiago Macieira wrote:
> > -#ifdef __cplusplus
> > -}
> > -#endif
>
> Out of curiosity: why are you compiling C sources as C++?
>
> Is that the Arduino compiler?
I wasn’t, I just noticed this leftover from a previous copy (likely the
file creation),
On 11/07/2016 23:26, Emil Velikov wrote:
On 4 July 2016 at 15:00, Quentin Glidic wrote:
From: Quentin Glidic
Signed-off-by: Quentin Glidic
---
libweston/gl-renderer.c | 2 +-
1 file changed, 1
xdg-foreign is a protocol meant to enable setting up inter surface
relationships across clients. Potential use cases are out-of-process
dialogs, such as file dialogs, meant to be used by sandboxed processes
that may not have the access it needs to implement such dialogs.
It works by enabling a
The reduction in range limits does have an effect for color values,
which are expressed as hexadecimal values from 0x to
0x. By limiting the range to INT_MAX, color values of
0x8000 and up are in fact lost.
This reverts commit 6351fb08c2e302f8696b2022830e5317e7219c39.
On Wed, Jul 13, 2016 at 01:27:29PM -0700, Bryce Harrington wrote:
> The reduction in range limits does have an effect for color values,
> which are expressed as hexadecimal values from 0x to
> 0x. By limiting the range to INT_MAX, color values of
> 0x8000 and up are in fact
On Jul 13, 2016, at 2:10 PM, Bryce Harrington wrote:
>
> On Wed, Jul 13, 2016 at 01:27:29PM -0700, Bryce Harrington wrote:
>> The reduction in range limits does have an effect for color values,
>> which are expressed as hexadecimal values from 0x to
>> 0x.
On Mon, Jul 11, 2016 at 05:13:34PM +0200, Carlos Garnacho wrote:
> From: Peter Hutterer
>
> Signed-off-by: Peter Hutterer
> Reviewed-by: Jason Gerecke
> Reviewed-by: Carlos Garnacho
Reviewed-by:
On Wed, 13 Jul 2016 14:27:17 -0700
Yong Bakos wrote:
> On Jul 13, 2016, at 2:10 PM, Bryce Harrington wrote:
> >
> > On Wed, Jul 13, 2016 at 01:27:29PM -0700, Bryce Harrington wrote:
> >> The reduction in range limits does have an effect for
On Jul 13, 2016, at 1:27 PM, Bryce Harrington wrote:
>
> The reduction in range limits does have an effect for color values,
> which are expressed as hexadecimal values from 0x to
> 0x. By limiting the range to INT_MAX, color values of
> 0x8000 and up
On Wed, Jul 13, 2016 at 02:12:43PM -0700, Yong Bakos wrote:
> On Jul 13, 2016, at 1:27 PM, Bryce Harrington wrote:
> >
> > The reduction in range limits does have an effect for color values,
> > which are expressed as hexadecimal values from 0x to
> > 0x.
On Mon, Jul 11, 2016 at 05:13:33PM +0200, Carlos Garnacho wrote:
> From: Peter Hutterer
>
> This is a straightforward copy/paste with a _v1 -> _v2 rename. No functional
> changes otherwise.
>
> Signed-off-by: Peter Hutterer
> Reviewed-by:
On Mon, Jul 11, 2016 at 05:13:35PM +0200, Carlos Garnacho wrote:
> From: Peter Hutterer
>
> The initial approach was to allow one surface to be re-used between tools,
> seats and even used together as wl_pointer cursor surface. This has a few
> drawbacks, most of which
Previously weston_config_section_get_uint was serving dual purpose for
parsing both unsigned decimal integer values (ids, counts, seconds,
etc.) and hexadecimal values (colors), by relying on strtoul's
auto-detection mechanism.
However, this usage is unable to catch certain kinds of error
[With hexadecimal color values now handled via their own routine,
re-introduce the negative unsigned numbers fix.]
strtoul() has a side effect that when given a string representing a
negative number, it returns a negated version as the value, and does not
flag an error. IOW, strtoul("-42", )
On Wed, Jul 13, 2016 at 02:27:17PM -0700, Yong Bakos wrote:
> On Jul 13, 2016, at 2:10 PM, Bryce Harrington wrote:
> >
> > On Wed, Jul 13, 2016 at 01:27:29PM -0700, Bryce Harrington wrote:
> >> The reduction in range limits does have an effect for color values,
> >> which
Hi,
On 13-07-16 01:51, Peter Hutterer wrote:
All Dell touchpas appear to have a visual marker on their touchpads. With a
visible marker our middle button can (and should) be much smaller since we
can rely on users to hit the button precisely.
https://bugs.freedesktop.org/show_bug.cgi?id=96710
On Sun, 10 Jul 2016 14:34:28 +0200 (CEST)
Jan Engelhardt wrote:
> On Sunday 2016-07-10 13:13, Quentin Glidic wrote:
> >
> > If we install only one .pc file:
> > - You cannot develop against an old version.
>
> I do not feel that is true. If you have Berkeley DB 4.5 in tarball
Dear All,
Seeing the below wayland log without above workaround focus is going 0
to surface. I think it means surface is failing to grab the touch
focus. What could be the reasons of focus not getting setup?
I think this [3687363.407] ivi_input@19.input_focus(90, 4, 0) need to
be [3687363.407]
On Wednesday 2016-07-13 13:54, Pekka Paalanen wrote:
>
>I think Quentin raised a good point, though. In source-based
>distros, well, in Gentoo at least which I use almost exclusively,
>there are no separate -devel packages.
A package is, abstractly, merely a selected subset of `make install`
21 matches
Mail list logo