You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with tree-store:set aka gtk_tree_store_set_valuesv, it uses gint* to receive a list of columns. Currently guile-gi expects to receive a bytevector. For IN arguments, we could support converting Scheme lists of integers to gint* arrays make such API easier on use.
This could be extended to the multiple integer and real number types
This would be a slow path, but, in the case of tree-store:set these C arrays are expected to be quite short.
The text was updated successfully, but these errors were encountered:
Is there a reason to do this internally rather than using list->[us]XX-vector, the procedures from (gi util) or even the [us]XXvector notation? Doing that would not only complicate the logic inside gig_argument, but also the creation of functions as we'd have to create any number of overrides for list/bytevector equivalences [not just those for optional arguments].
When working with
tree-store:set
akagtk_tree_store_set_valuesv
, it usesgint*
to receive a list of columns. Currently guile-gi expects to receive a bytevector. For IN arguments, we could support converting Scheme lists of integers togint*
arrays make such API easier on use.This could be extended to the multiple integer and real number types
This would be a slow path, but, in the case of
tree-store:set
these C arrays are expected to be quite short.The text was updated successfully, but these errors were encountered: