0000205: Setting priority on multiple servers while sorted by priority fails

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000205

aMule

Servers

public

2004-11-21 11:20

2005-01-28 18:05

Reporter

ken

Assigned To

Xaignar

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

fixed

Platform

Mac

OS X

OS Version

10.3.5

Product Version

Target Version

Fixed in Version

Summary

0000205: Setting priority on multiple servers while sorted by priority fails

Description

Attempting to set the priority on multiple servers simultaneously while the server list is sorted by priority fails because server list entries are re-ordered while being iterated.

Steps To Reproduce

Run amule, view Servers screen.
Set several servers to low priority, several to normal, and several to high.
Sort the server list by priority so that low priority servers are at the top.
Select all the low priority servers.
Right-click (command-click) and choose Priority -> Normal from the context menu.
Observe that some of the selected servers have their priority changed and are resorted to group with other Normal servers, but that some of the selected servers do *not* have their priority changed and remain at the top of the server list.

Tags

No tags attached.

Fixed in Revision

Operating System

Attached Files

Relationships

Notes
(0000517) Xaignar (manager) 2005-01-16 18:20	Should be fixed in CVS as of now. Note that the static column suffered from the same problem, which also has been fixed now.

(0000558) phoenix (developer) 2005-01-26 03:58	Ken, can you confirm that this issue is fixed?

(0000576) ken (developer) 2005-01-28 16:36	Confirmed as fixed.

(0000578) phoenix (developer) 2005-01-28 18:05	Ok

Issue History
Date Modified	Username	Field	Change
2004-11-21 11:20	ken	New Issue
2005-01-15 02:00	Xaignar	Status	new => assigned
2005-01-15 02:00	Xaignar	Assigned To	=> Xaignar
2005-01-16 18:20	Xaignar	Status	assigned => resolved
2005-01-16 18:20	Xaignar	Resolution	open => fixed
2005-01-16 18:20	Xaignar	Note Added: 0000517
2005-01-26 03:58	phoenix	Status	resolved => feedback
2005-01-26 03:58	phoenix	Resolution	fixed => reopened
2005-01-26 03:58	phoenix	Note Added: 0000558
2005-01-27 13:12	phoenix	Resolution	reopened => fixed
2005-01-28 16:36	ken	Status	feedback => resolved
2005-01-28 16:36	ken	Note Added: 0000576
2005-01-28 18:05	phoenix	Status	resolved => closed
2005-01-28 18:05	phoenix	Note Added: 0000578