I try to create a binding from GNOME official PanelApplet-4.0.gir to
libpanelapplet-4.0.vapi.
Vapi generation success, but the header file name is wrong(always
"PanelApplet-4.0.h"). I tried to change it by adding a new file named
"libpanelapplet-4.0.metadata" in the same directory:
PanelApplet
2012/1/4 Tal Hadad
>
> I try to create a binding from GNOME official PanelApplet-4.0.gir to
> libpanelapplet-4.0.vapi.
> Vapi generation success, but the header file name is wrong(always
> "PanelApplet-4.0.h"). I tried to change it by adding a new file named
> "libpanelapplet-4.0.metadata" in the
Thanks, it works as expected.
But I were reading other manual:
http://live.gnome.org/Vala/Manual/GIDL%20metadata%20format
Since it was mention in:
http://live.gnome.org/Vala/Bindings
What is the different between this two "metadata" formats?
Thanks
Tal
Date: Wed, 4 Jan 2012 11:40:08 +0100
Sub
Thanks, but I have a new problem:
How can I access to class methods? This line doesn't work and raise warning:
PanelApplet.add_preferences hidden=true
Tal
Date: Wed, 4 Jan 2012 12:03:58 +0100
Subject: Re: [Vala] vapigen ignores .metadata
From: lethalma...@gmail.com
To: tal...@hotmail.com
2012/1
2012/1/4 Tal Hadad
>
> Thanks, but I have a new problem:
> How can I access to class methods? This line doesn't work and raise
> warning:
> PanelApplet.add_preferences hidden=true
>
1) Please _always_ write down any warning or error
2) Use skip instead of hidden=true
--
www.debian.org - The Un
> 1) Please _always_ write down any warning or error
> 2) Use skip instead of hidden=true
Result:
PanelApplet-4.0.metadata:2.13-2.27: warning: metadata never used
PanelApplet.add_preferences skip=true
^^^
Generation succeeded - 1 warning(s)
Date: Wed, 4 Jan 2012 12:51:06
Sorry for spamming but it seems that it's a bug without clear product
which is fully "responsible" for the problem (see Ryan's comment[1]). On
the other hand it affects all libgee newer then 0.4.0 release and hence
it is probably blocker on Gnome 3.4.
In summary the glib master become more restric
hi Maciej,
Thanks for bringing up this topic. I'm not exactly sure what the proper
way forward is, but you raise some interesting possibilities.
On Thu, 2012-01-05 at 01:32 +0100, Maciej Marcin Piechotka wrote:
> I don't think I can fix on libgee side without breaking API/ABI (at
> least I don't
On Thu, Jan 5, 2012 at 10:40 AM, Ryan Lortie wrote:
> hi Maciej,
>
> Thanks for bringing up this topic. I'm not exactly sure what the proper
> way forward is, but you raise some interesting possibilities.
>
> On Thu, 2012-01-05 at 01:32 +0100, Maciej Marcin Piechotka wrote:
>> I don't think I can
