[hafqa] [hafqa] [Bug 2195] New: Request to change type of argument 'id' in HildonBreadCrumbTrail's push methods and signals

From: bugzilla-daemon at lists.maemo.org bugzilla-daemon at lists.maemo.org
Date: Thu Nov 1 16:49:48 EET 2007
https://bugs.maemo.org/show_bug.cgi?id=2195

           Summary: Request to change type of argument 'id' in
                    HildonBreadCrumbTrail's push methods and signals
           Product: System software
           Version: 4.0
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: Low
         Component: hildon-libs
        AssignedTo: michael.kostrzewa at nokia.com
        ReportedBy: lauro.neto at openbossa.org
         QAContact: hildon-libs-bugs at maemo.org


When pushing a new crumb, there's an argument 'id', a gpointer, which is passed
back when that crumb is clicked, in the signal 'crumb-clicked'.

The problem is that it doesn't works with PyGtk default marshalling process.
The resulting python function call returns an opaque type 'gpointer'.

Changing the 'id' type to 'const gchar *' solves this, as it will be converted
to a simple python string.

Also, I think that a basic type like string or int is the correct choice for an
id field and choosing only one type eases the binding process for any language.
An gpointer could be provided as an "user_data" argument, like in
g_object_connect.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the hafqa mailing list