Merge lp:~oliwee/openlp/bug-1247025 into lp:openlp
Proposed by
Oliver Wieland
Status: | Rejected |
---|---|
Rejected by: | Tim Bentley |
Proposed branch: | lp:~oliwee/openlp/bug-1247025 |
Merge into: | lp:openlp |
Diff against target: |
85 lines (+24/-5) 2 files modified
openlp/core/lib/mediamanageritem.py (+5/-0) openlp/core/ui/servicemanager.py (+19/-5) |
To merge this branch: | bzr merge lp:~oliwee/openlp/bug-1247025 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Raoul Snyman | Needs Information | ||
Tim Bentley | Pending | ||
Oliver Wieland | Pending | ||
Review via email: mp+193592@code.launchpad.net |
This proposal supersedes a proposal from 2013-11-01.
Description of the change
Fixes bug #1247025
Changes the position where a new item will be inserted in the service list via drag'n'drop
Example: service list
A
B
C
item D will be dropped on B's position:
A
B D
C
Before:
A
B
D
C
After:
A
D
B
C
To post a comment you must log in.
Unmerged revisions
- 2314. By Oliver Wieland
-
Make adding items to service list via context menu work again
Added setter / getter for drop_position to class ServiceManager - 2313. By Oliver Wieland
-
fix insertion on position '0'
- 2312. By Oliver Wieland
-
fix inserting multiple selection into service list via drag'n'drop
- 2311. By Oliver Wieland
-
correction of setting position
- 2310. By Oliver Wieland
-
changed insert position for inserting an item to the service list via drag'n'drop
This merge proposal works on all positions in the service list, but not on position '0'. This is because in servicemananage r.py. line 1300, the position 0 will be handled in a special way.
But I have no idea when this case would be true (without my changes). Could somebody please explain if this case becomes true at all?