>
> On Fri, 2016-10-28 at 06:46 -0400, Frediano Ziglio wrote:
> > >
> > >
> > > In commit beec1b41, we manually limited this property value in
> > > _set_property(). But there's a simpler way to do it: via the param
> > > spec
> > > for the property.
> > >
> > > This also means that we can remo
On Fri, 2016-10-28 at 06:46 -0400, Frediano Ziglio wrote:
> >
> >
> > In commit beec1b41, we manually limited this property value in
> > _set_property(). But there's a simpler way to do it: via the param
> > spec
> > for the property.
> >
> > This also means that we can remove the warning log in
>
> In commit beec1b41, we manually limited this property value in
> _set_property(). But there's a simpler way to do it: via the param spec
> for the property.
>
> This also means that we can remove the warning log in red_worker_new()
> since GObject will automatically warn if a property is assi
In commit beec1b41, we manually limited this property value in
_set_property(). But there's a simpler way to do it: via the param spec
for the property.
This also means that we can remove the warning log in red_worker_new()
since GObject will automatically warn if a property is assigned a value
ou
