Copying would be a helpful thing. I ran into similar problems. There is a workaround. My copy/paste operation core (sorry, this is c/p from my application so no setup code shown): cell = sheet.cell_fetch(col, row) d_sheet, d_cell is the destination to copy to. You essentially have to work with parts of a cell. patches I sent privately. I think if certain core functions are done first it will enable development that would uncover other problems. I have a personal development note document I will share here, since apparently rough drafts are OK to some of you and hint at problems: Gnome Introspection notes - not part of the application - used scanner driven code - comments are code - function names influence introspection interface - names with "new" mostly result in constructor interfaces that return full-ownership objects that are easily usable. - Comments may not export usable interface and this will not show up as a bug in the application. e.g. allow-none/nullable optional values. (* I previously described this about inserting "allow-none" in the defintions) https://wiki.gnome.org/Projects/GObjectIntrospection#Annotation_System https://wiki.gnome.org/Projects/GObjectIntrospection/Annotations Python GI API Reference https://lazka.github.io/pgi-docs/ Python and introspection - Applications are C, python is not - Objects needs to be converted between the two, normally transparent but sometimes results in unexpected behavior. Memory Management - not all objects get exported in a directly usable way - in .gir file, object definitions tagged return-value transfer-ownership="full" are directly usable python objects - other objects may need reference or memory management and can trigger segfaults On 04/11/2018 04:42 PM, Morten Welinder
wrote:
|