maemo.org Bugzilla – Bug 7603
HildonTouchSelector example has wrong parameters in callback function
Last modified: 2010-05-17 16:49:43 UTC
You need to
before you can comment on or make changes to this bug.
SOFTWARE VERSION: maemo5 hildon-example
EXACT STEPS LEADING TO PROBLEM:
1. Use the hildon touch selector example from either the maemoexamples package,
in the hildon-examples directory
or the documentation page
2. In the g_signal_connect call for the "changed" signal, give a value for the
user_data parameter instead of NULL.
3. In the signal callback function, read the user_data parameter back.
EXPECTED OUTCOME: The user_data should be the value given to the
ACTUAL OUTCOME: The user_data is NULL.
OTHER COMMENTS: This happen because the example is wrong: the signal callback
function is missing a gint column parameter, which causes the user_data
parameter to receive it instead. This is not a bug in the SDK but a mistake in
the example. Since the user_data parameter is ignored in the original code, the
example works fine, but it leads to bugs and/or crashes as soon as one extends
the example code to pass along user data.
Indeed, these docs are wrong. But that's a bug in the documentation, not in the
examples that are part of the library itself. I have no idea who maintains that
Maemo examples in Garage are part of Maemo documentation. I assign this to Aapi
for him to check.
Fixed. The signature is now HildonTouchSelector*, gint, gpointer. (Thanks
[Rearrangement of Documentation bug reports.]
Mass-moving old closed Developer Platform > Documentation tickets.
You can filter bugmail by searching for this comment.