When using Keyboard-shortcuts to assign a resource, an additional resource is assigned

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open a file including resources in GanttProject
2. Go to a project and open its "Properties". 
3. Go to the resource-tab.
4. Click on an empty tab to add a new resource. A name is filled in from the 
list. Enter the first letter of a different name, e.g. "K". A resource starting 
with "K" shows up (let's call him "Karl").
5. Scroll down to a different resource starting with "K", for example "Kyle" 
and enter the amount of work you want him to work on something.
6. Now "Kyle" is selected correctly, "Karl" is no longer visible, everything is 
perfect. Close the project view.
7. Go back into the project and its resource-view.
8. You now see "Karl" and "Kyle", and "Karl" is assigned 100% to this project, 
which totally messes up his calculations.

What is the expected output? What do you see instead?
For the example above, I expect to see only Kyle, not Karl.

What version of the product are you using? On what operating system?
GanttProject 2.0.10 on Windows. Tried with Praha 2nd Beta, same problem there.

Please provide any additional information below.
This problem means that I effectively cannot use keyboard-shortcuts when 
selecting resources - which is a real pain when you have as many as I do (more 
than 50)...

Original issue reported on code.google.com by misu2...@gmail.com on 6 Oct 2011 at 12:53

[GoogleCodeExporter]

When you say "project", do you mean "task"?

I reproduced it with HouseBuildingSample, using a smilar scenario: open 
properties of "Architecture design" task, switch to "Resources", click in the 
empty row, type "J" (Jack House gets selected), then click the drop down, 
select  "John Silver" and click Ok. What happens is that both Jack and John are 
assigned now to the task

Original comment by dbarashev on 6 Oct 2011 at 6:53

• Changed state: Accepted
• Added labels: Tasks, UI

[GoogleCodeExporter]

Yes, I do mean task. Sorry about the confusion.

Original comment by misu2...@gmail.com on 6 Oct 2011 at 8:15

[GoogleCodeExporter]

I am attaching the smallest patch that fixes the problem for me. Unfortunately, 
it still leaves the Mutators broken for deleting assignments (as in: when you 
press delete, the assignment is deleted immediately, rather than at the point 
in time when the user presses OK). 

I tried to make them work, but there is still an edge-case that is broken :-(. 
Will see if I can find the time to finally fix it.

Original comment by misu2...@gmail.com on 7 Oct 2011 at 10:35

Attachments:

• SmallChanges.patch

[GoogleCodeExporter]

This issue was closed by revision b01fc3cc9597.

Original comment by dbarashev on 10 Oct 2011 at 11:36

• Changed state: Fixed

[GoogleCodeExporter]

This issue was closed by revision b01fc3cc9597.

Original comment by dbarashev on 10 Oct 2011 at 11:40

[GoogleCodeExporter]

This issue was closed by revision b01fc3cc9597.

Original comment by dbarashev on 10 Oct 2011 at 11:44

[GoogleCodeExporter]

This issue was closed by revision b01fc3cc9597.

Original comment by dbarashev on 11 Oct 2011 at 12:24

[GoogleCodeExporter]

This issue was closed by revision b01fc3cc9597.

Original comment by dbarashev on 11 Oct 2011 at 12:28

[GoogleCodeExporter]

Original comment by dbarashev on 22 Sep 2014 at 12:22

• Changed state: Verified