Zero-distance guide point can't be selected, snapped to, deleted

bug
guidepoints
tapemeasure

#1

I created a couple of guide points like this:

  1. Click an existing point.
  2. Move mouse in a specific direction (negative blue axis in my case).
  3. Type the distance “0mm” and hit Enter.
    As expected a guid point appeared at the location that was clicked in step 1.
    I subsequently removed the pre-existing point from step 1, and can still see the new zero-distance guide point.
    But this guid point can’t be interacted with in any way. I can’t snap to it. I can’t select it. I can’t delete it.

Is this a bug? In that case, where should I report it?

How can I get rid of these guide points? (Regardless if it’s a bug or not, I want to get rid of them).

Regards,
Kjell


Zero-distance guide point can't be interacted with in any way
#2

Edit menu, delete guides.


#3

Nice, but I have a lot of other guides that I want to keep.


#4

Well, don’t know what to tell you, I followed your method and created a guide point that I have no problem selecting and deleting.


#5

Alright. Bug in the model then, perhaps. I’ll try save and restart.


#6

If you can share the problem model the rest of us can see if we get the same results.

Edit: On second thought, I can reproduce what you saw:

dead%20guide


#7

Yes, that’s appears to be the same glitch. :slight_smile:


#8

What’s even odder is that I can find that guide point and add it to the selection using Ruby. That suggests it is indeed a glitch somewhere in the GUI.


#9

Very strange, the first few times I tried it I had no problem interacting with the guide point, now it happens every time.


#10

And more: Edit->Select All can’t get the GP either!


#11

OK, so it seems we should conclude that it’s a bug. Where should I report it?


#12

Wow, that is weird!


#13

I reported it here, with a backref to this thread:


Thanks folks for helping me with it, showing that it’s a reproducible bug.


#14

Here’s a way to select the elusive zombie GP.
@TIG’s Selection Hide/Show plugin has an Invert Selection command.
Select All > Invert Selection … and the unselectable Guide Point is selected.

TIG: Selection Hide/Show v1.1
https://sketchucation.com/pluginstore?pln=SelectionHideShow


#15

Which agrees with my observation that the guide exists in the model’s entities and can be accessed via Ruby API. It seems the bug is in the GUI.


#16

I suspect it is to do with the lack of a tail. I think all native guide points are at the end of a tail aren’t they, only extensions create actual naked guide points.
At least I can’t think, off the top of my head, a native way to make a guide point without a tail.

Edit: No, find center will, hmm so I’m probably wrong.


#17

Yes, you’re wrong. The steps I use will create a guide point without a tail, and require no extensions.


#18

I think you missed my point. Normally there would be a tail but using 0mm forces the creation of a tailed guidepoint with no space for the tail.


#19

I have the same problem I cut my model from around the points and copied to a new template, when everything was deleted from the model I had only 3 guide points and still totaled over 18000kb They are annoying little devils.


#20

That’s an interesting speculation. There are details of guide points that are not exposed in the Ruby API, so there’s no useful way to investigate. For example, in the Ruby API if you add a ConstructionPoint (the API name for a guide point), you get just a bare point, no tail. In the Ruby API there is no such object as a guide point with a tail! If you want a tail you have to add a finite-length ConstructionLine with appropriate ends. Conversely, in the GUI aside from the trick demonstrated in this topic there is no way to create a guide point without a tail (ok, find center will also do it). Obviously the back-end has a more complex structure to handle both the guide point and the tail as a unit, but this structure is not fully exposed via the Ruby API. My suspicion is that when you cause the GUI to create a zero-length tail the back end gets confused about how to handle the (in its view) defective tail, and that blocks selection of the guide point.

It’s clearly a bug. The question, then, is whether the development team will see it as important enough to assign anyone to fix it.