Click-selecting an item selects the incorrect item

[GoogleCodeExporter]

I'm not sure how to 100% reliably reproduce this, but it's a seriously annoying 
bug.

What happens is that (for any layout with a non-trivial number of components) 
there will eventually be one component that, when you click on it, will not be 
highlighted.  Instead, some other component will get highlighted instead. It's 
actually impossible to select the item that you want.

You can make this go away by saving the file, closing the program, then 
restarting and reopening.  Forcing garbage collection may also help, but I'm 
not sure if this works 100% of the time.

The other way you can see this bug is by highlighting a group of components in 
an area by the click-sweep method.  Often you will see a component that is not 
in the selected area light up.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Whenever possible, please attach the latest log file. It will
provide valuable information when trying to reproduce and locate the
problem. Log files can be found in the log directory under the main
application directory and are marked with date and time.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by pmfawc...@gmail.com on 19 Jan 2012 at 5:52

[GoogleCodeExporter]

Agreed, I've just created a test file (attached) and it happens. I created one 
component and all the others were copied and pasted from that. Problem appeared 
immediately - maybe the selection has somehow hungover. I then shut and 
re-opened it and it was ok, but if I selected and de-selected some components 
some remained selected.  

Original comment by ChrisofB...@gmail.com on 19 Jan 2012 at 6:37

Attachments:

• test.diy

[GoogleCodeExporter]

Here's a further clue... sometimes you will notice the problem when you select 
an item... the wrong item will be selected right away.  But other times, 
clicking will select the desired item...and it will only be when you try and 
move the item, that the non-desired item suddenly becomes selected and moves! 
Maybe two different but related problems?

I can confirm now that forcing garbage collection does NOT always fix this, but 
sometimes does.

Original comment by pmfawc...@gmail.com on 25 Jan 2012 at 6:03

[GoogleCodeExporter]

it's actually related with zooming, has nothing to do with the number of 
components or garbage collections, but it's easier to spot on crowded boards. 
For the time being please refrain from using anything but 100% zoom, and I'll 
try to rectify
Cheers

Original comment by bancika@gmail.com on 2 Feb 2012 at 1:38

[GoogleCodeExporter]

Original comment by bancika@gmail.com on 3 Feb 2012 at 3:47

• Changed state: Fixed