Bug 788545 - GtkTreeModel.iter_previous and iter_next have confusingly different behaviour
Summary: GtkTreeModel.iter_previous and iter_next have confusingly different behaviour
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pygobject3
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-08 12:17 UTC by Vratislav Podzimek
Modified: 2013-03-13 04:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-20 10:40:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Vratislav Podzimek 2012-02-08 12:17:05 UTC 
Description of problem:
While GtkTreeModel.iter_next(itr) has an override and does not modify itr, iter_previous(itr) modifies it. Since both these functions behave in the same way in the original C code I would expect this also in the Python gi binding.

Version-Release number of selected component (if applicable):
pygobject3-3.0.3-1.fc16.x86_64

How reproducible:
100%

Steps to Reproduce:
1. try to use iter_next(itr) and iter_previous(itr) from Python and see what's happening to itr
  
Actual results:
confusing difference in behaviour

Expected results:
no confusing difference -- preserving itr in both cases would be better
Comment 1 Vratislav Podzimek 2012-10-20 10:40:10 UTC 
This is fixed in recent rawhide versions.
Note You need to log in before you can comment on or make changes to this bug.