After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 579466 - gtk_entry_completion_insert_action documentation is misleading
gtk_entry_completion_insert_action documentation is misleading
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkEntry
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-04-19 00:27 UTC by Christian Dywan
Modified: 2018-02-10 03:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Clarify index in documentation (866 bytes, patch)
2009-09-04 12:32 UTC, Christian Dywan
none Details | Review

Description Christian Dywan 2009-04-19 00:27:52 UTC
I recently started to use completion "actions" in a GtkEntryCompletion. I have an array that, so I thought, each element would map to an "action" in the completion.

It turns out deleting items and adding new items later on leads to curious tree iter failures.

So the documentation says "Deletes the action at @index_ from @completion's action list." which I understand as each action having an index which is associated to a label, and can later be deleted or overwritten. But it turns out in practise 'index' is a *position* in a list.

I suggest the documentation should be clearer about 'index' actually being a relative position depending on the actions currently present.
Comment 1 Christian Dywan 2009-09-04 12:32:03 UTC
Created attachment 142470 [details] [review]
Clarify index in documentation
Comment 2 Matthias Clasen 2009-09-04 14:26:24 UTC
Sounds ok to me. It would be more useful if it also contained a hint for how one can learn about an actions current index.
Comment 3 Christian Dywan 2009-09-04 15:48:16 UTC
I wouldn't know of a way to find that out.
Comment 4 Matthias Clasen 2018-02-10 03:22:47 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.