On 10/11/2013 05:07 PM, Thomas Olson wrote:
Hello,
I've encountered this several times where the Vala compiler will
misinterpret a four byte hex literal as a long or int64. For example
0x requires a cast in order to be assigned to a uint32. Is
this a known bug?
Thanks,
Tom
Hello,
I've encountered this several times where the Vala compiler will
misinterpret a four byte hex literal as a long or int64. For example
0x requires a cast in order to be assigned to a uint32. Is this
a known bug?
Thanks,
Tom
___
v
Oh, interesting! I updated the page, hope this is correct:
https://wiki.gnome.org/action/info/Vala/Tutorial?action=diff&rev2=242&rev1=241
I also noticed that doing this as a top-level function, i.e naming a
function outside any class or namespace something beginning with a
digit, generates faulty
Hey Simon,
The overview is outdated:
public class Foo : Object {
// Identifier = "0foo"
public string @0foo {get;set;}
}
Regards,
Florian
On 11 October 2013 10:46, Simon Kågedal Reimer wrote:
> Hi,
>
> On Fri, Oct 11, 2013 at 9:34 AM, Tal Hadad wrote:
>> First time I hear not all pr
2013/10/11 Tal Hadad
> > Of course you would have to _declare_ the 'notify' signal.
> I suppose that by "declare" you mean invoking notify("property")
> inside the setter.
>
>
No, I mean declaring it such as:
class Foo {
public signal void my_prop_notify(int value);
}
Jonas
> Of course you would have to _declare_ the 'notify' signal.
I suppose that by "declare" you mean invoking notify("property")
inside the setter.
Thank everyone for the full answer.
Tal
Date: Fri, 11 Oct 2013 16:25:27 +0200
Subject: Re: [Vala] Properties == GObject properties?
From: nyocu...@gmail
2013/10/11 Tal Hadad
> > Hi,
> >
> > On Fri, Oct 11, 2013 at 9:34 AM, Tal Hadad wrote:
> > > First time I hear not all properties are GObject.
> > >
> > > Suppose I have this property:
> > >
> > > ...
> > > public int 1numbered { get; set; }
> > > ...
> > >
> > > This is not a GObject property,
> Hi,
>
> On Fri, Oct 11, 2013 at 9:34 AM, Tal Hadad wrote:
> > First time I hear not all properties are GObject.
> >
> > Suppose I have this property:
> >
> > ...
> > public int 1numbered { get; set; }
> > ...
> >
> > This is not a GObject property, since it's started with a number.
>
> You ca
Hi,
On Fri, Oct 11, 2013 at 9:34 AM, Tal Hadad wrote:
> First time I hear not all properties are GObject.
>
> Suppose I have this property:
>
> ...
> public int 1numbered { get; set; }
> ...
>
> This is not a GObject property, since it's started with a number.
You can't have that at all, see
ht
First time I hear not all properties are GObject.
Suppose I have this property:
...
public int 1numbered { get; set; }
...
This is not a GObject property, since it's started with a number.
Does it mean that I couldn't connect to notify["1numbered"] signal?
In case that I can't connect to notify
10 matches
Mail list logo