The un-erasable "one-dot line" bug can still occur.

[GoogleCodeExporter]

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:53

[GoogleCodeExporter]

Sorry, hit return soon.. I don't think you can invoke it anymore when you draw 
a component as was the case before... It may be happening now though when you 
move something that is attached to a wire in such a way that the wire is 
reduced to a single line. 

Original comment by pmfawc...@gmail.com on 19 Jan 2012 at 5:55

[GoogleCodeExporter]

I still get this myself.
Version 3.0.9
Windows 7 

Work-Around:
1. SAVE FILE FIRST.
2. Create another line in the same spot (but one that you can delete of course).
3. Give it a specific name.
4. Save file. Use a different name than the original.
5. Look in the .DIY file for that name.
6. Look for that specific name and find something like this (Numbers may be 
different):
(First one is across, second one is up and down)
      <points>
        <java.awt.Point x="2.3" y="4.5"/>
        <java.awt.Point x="2.5" y="4.5"/>
      </points>

Or this:
      <points>
        <java.awt.Point x="2.3" y="4.5"/>
        <java.awt.Point x="2.3" y="4.7"/>
      </points>

7. Then look for one that looks like this, with the same numbers as the line 
you just made:

      <points>
        <java.awt.Point x="2.3" y="4.5"/>
        <java.awt.Point x="2.3" y="4.5"/>
      </points>

8. Change the numbers, like so:

      <points>
        <java.awt.Point x="2.3" y="4.9"/>
        <java.awt.Point x="2.5" y="4.5"/>
      </points>

9. Trace is now select-able!

Original comment by CodeMo...@gmail.com on 26 Jan 2012 at 1:16

[GoogleCodeExporter]

I have only had this issue with traces.

Original comment by CodeMo...@gmail.com on 26 Jan 2012 at 1:17

[GoogleCodeExporter]

Issue 131 has been merged into this issue.

Original comment by bancika@gmail.com on 24 Mar 2012 at 11:03

[GoogleCodeExporter]

Original comment by bancika@gmail.com on 31 Aug 2012 at 2:00

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This is still a problem in 3.26.0.  This becomes incredibly annoying and time 
wasting when the "dot" is accidentally created by moving things around.  Once 
created, that dot is not only un-erasable, but also immovable, so if you select 
a number of things to move and the dot is among them (which you cannot see), 
that selection will not move.

Original comment by gordtran...@gmail.com on 24 May 2013 at 8:53

[GoogleCodeExporter]

I ran into this problem as well on version 3.27.0 (Win 7, 32 bit). The way I 
corrected it was to right-click on the Trace button in the tool bar, which 
selects all the traces. Then I 'grabbed' the control point of one of the 
offending traces and extended the trace to an actual line then deleted that 
trace altogether.

Would be nice to not have to do that, but it works anyway.

Original comment by geoff.n7...@gmail.com on 23 Jun 2013 at 7:57