breakatpoint fails to get right osnap

[vandenoosterkamp]

With the break at point command, the program doesn't behave correctly. When I specify midpoint it still picks endpoint. I then manually specify midpoint, not via osnap. When I copy the object to an empty drawing and do exactly the same thing it works fine. With some lisps I also get the message 'too many intersects for objectsnap' or similar. It's not a large drawing as such but it does have 40 xrefs loaded. I always keep only the layers I need visible, which is about 1/30th of the total. It seems to me there's some kind of object overflow? Moving the UCS so the break point is closer to the origin doesn't help either.

unloading 39 xrefs does not fix it. detaching 39 xrefs does but that is very much NOT the way I want to go.

[imadHabash]

Hi,

>> detaching 39 xrefs does...

As long as the issue is resolved by creating a new drawing and removing the xrefs, then the procedure is correct and there is no problem. However, the problem lies in something specific that prevents the breakpoint from being completed correctly.

I suggest to find that near xref which cause your issue.

[vandenoosterkamp]

Yes, in some overflow caused by to many objects for intersect. Osnap simply gives up at some point and on a dwg that works fine and fast due to clever usage of a whole lot of custom lisps so I can turn of 97% of the drawing so I can work fast there is still some misery in the background causing this.

I have no clue what you mean with 'near xref'.

When I freeze 97% of the layers that are not needed then this nasty bug is gone. So objects on a layer that is turned of are still counting in some weird object counter in the background that at some points needs to cause bugs and nag about 'to many objects' while when I freeze those layer those objects are appearantly not counted for that acad system failure of 'to many objects'.

Will this nasty, probably 30 year old badly written code ever be rewritten in a better way so this will go away? Of course I understand that you cannot stash objects eternally in 1 single dwg allthough I would very much appreciate it if that could be done. 

I wasted quite some time in rewriting lisps so instead of just turning 97% of that 97% is also frozen now. 

workarounds, workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds workarounds, I have hundreds by now due to lacking functionality 

[ChicagoLooper]

@vandenoosterkamp 
You’re right. If your drawing is ‘busy’ with too many snap points, AutoCAD will get confused, ignore your target, then give a snap you don’t want. You could turn off some snaps OR you can use ‘Snap Overrides’ in the middle of ‘break at point’ command. <<This will temporarily override your osnap settings and only obey your target snap location.>> 

For example:

Break at Point command=>Shift+Right click=>Select Midpoint from shortcut menu=>Click target Midpoint (refer to image.)

 

 

[vandenoosterkamp]

"I then manually specify midpoint" first post... I try all basis stuff before going here. Going here is merely psuchological anyway to write it off. My shrink told that is better than breaking stuff in despair