Thanks for the patch, but this can be done even without adding anything
to the library. Something like:
/**
* Workbook:
* @wb_views: (content-type WorkbookView):
**/
I'll commit that later today.
Jean
Le mercredi 06 novembre 2013 à 11:36 +0200, Anatoly Asviyan a écrit :
> Hi Jean
>
> Th
Hi Jean
Thanks for explanation.I agree that a clean way is to tell introspection
what types each GPtrArray stores, but I do not know how to do it. So I
wrote two access functions that return explicit type - and it worked!
In python console, you can do smth like this
from gi.repository import Gnm
It should be possible to get a WorkbookControl from a Workbook with code
such as:
view=workbook.wb_views[0]
control=view.wb_controls[0]
but it currently does not work becaus we did not tell introspection what
objects are stored in the arrays (this can be easily fixed), and I don't
think it is pos
2013/11/5 Jean Bréfort
> I suppose it should work the same way, but I'm not an expert.
In old python API, WokbookControl was never exposed to python. It (WBCGtk)
was used within C code to get correct sheet, then only sheet object was
exported back to python
Is it possible to get WorkbookContr
I suppose it should work the same way, but I'm not an expert. Note that
the introspection mechanism works from outside gnumeric as well.
Jean
Le mardi 05 novembre 2013 à 11:33 +0200, Anatoly Asviyan a écrit :
>
>
>
> 2013/11/1 Jean Brefort
> Hi Anatoly,
>
> If you are
2013/11/1 Jean Brefort
> Hi Anatoly,
>
> If you are using 1.12.x, you might also imprt the Gnm module from the
> gogject intreospection repository. That would give you access to many
> more functionalities (though the naming conventions in Gnumeric are not
> always optimal and make introspection
Hi Anatoly,
If you are using 1.12.x, you might also imprt the Gnm module from the
gogject intreospection repository. That would give you access to many
more functionalities (though the naming conventions in Gnumeric are not
always optimal and make introspection do stupid things).
from gi.repositi
