Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pygobject
pygobject
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 149
    • Issues 149
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • pygobjectpygobject
  • Issues
  • #281

Closed
Open
Opened Nov 29, 2018 by Cian Wilson@cianwilson
  • Report abuse
  • New issue
Report abuse New issue

TreeStore.insert_before/after no longer behaves as documented when parent=None and row is provided.

Following 908d099c and !48 (merged) (included in release 3.29.1) TreeStore.insert_before/after can no longer be called with parent=None if row is provided. Under these circumstances insertion is performed using TreeStore._do_insert and TreeStore.insert_with_values, which take a positional argument relative to the parent but if the parent is None then this is interpreted as being relative to the root of the tree rather than the depth in the tree at which the sibling was.

This is a change in behavior from before !48 (merged) and contradicts (my interpretation of) the documentation (https://lazka.github.io/pgi-docs/#Gtk-3.0/classes/TreeStore.html#Gtk.TreeStore.insert_after), which states: "When sibling is set, parent is optional."

Assignee
Assign to
3.30
Milestone
3.30
Assign milestone
Time tracking
None
Due date
No due date
1
Labels
1. Bug
Assign labels
  • View project labels
Reference: GNOME/pygobject#281