"Snappy", more snap points for CamBam plugin

[GeoffreyGRoy]

I have been also intrigued by the option to hide the cursor and was interested in exploring other options.  After some practice, however, I am almost convinced that the the "hiding" actually works quite well, though I admit it is  a little counter intuitive.

Geoff

[dh42]

Hello

On other softs, the cursor change depending on the snap point encountered, the standard arrow is conserved but it has an additional symbol depending of the snap point  

http://www.rw-designer.com/online-cursor-editor

++
David

[dh42]

Eddy,
I see that tremendous slowness about every-other time I re-visit the snap features.

It is slowness, not 'grid'.  But it's so annoying that you can't really tell when you've actually snapped to a snap-point.

I'm running an old XP system, so some slowness is expected, but I've never seen the sort of jitter I'm getting now.

Lloyd

Hello

I just falls on the same problem ; on a "big" file, if snap to intersection is ON, the cursor don't follow the mouse moves and takes time to react.

I can't redo it on the video, but when working, CB freeze during 3 or 4s at a moment and the screen become "gray" (but I do not remember what I was doing when this problem appears)

so maybe it would be a good idea to disable the snap to intersections until it is really needed. (it seems that others snaps do not slow the things significantly ; at least on my PC)

++
David

[GeoffreyGRoy]

I think I have seen the same problem on a model with a large number of polylines (with many segments).  Disabling all snap options seems to fix the response.  The idea to have an option to disable/enable snapping (without changing the required selections)  sounds useful (maybe a menu bar item - like snap to grid)
Geoff

[EddyCurrent]

The idea to have an option to disable/enable snapping (without changing the required selections)  sounds useful (maybe a menu bar item - like snap to grid)
Geoff

Or maybe this in the "Plugins" menu called, "Snappy"   you didn't see that Geoff ?

[GeoffreyGRoy]

I know that I can select the snap options this way, but that means making 6 selections to disable Snappy, and then remembering which ones were changed to reset back again.  What would be nice would be an options to make Snappy go to sleep for a while, and when woken-up, remember the settings!
Geoff

[EddyCurrent]

Geoff,
The form is designed to remain open on the desktop if desired. Options can be enabled/disabled even in the middle of drawing a line, etc. I'm inclined to think that's adequate.

[dh42]

Geoff,
The form is designed to remain open on the desktop if desired. Options can be enabled/disabled even in the middle of drawing a line, etc. I'm inclined to think that's adequate.

Hello

Yes, it's what I show in the video on reply #107

++
David

[Dragonfly]

Hi Eddy,
I think I found a minor bug in the plugin. Happened with a newly opened .dxf file where all geometry consists of true lines and arcs instead of polylines. On trying to snap to a line CB raises an exception. Maybe the plugin should ignore geometry elements that are not native to CB if they are not converted to polylines.

[dh42]

Hello

I just tried the same with a simple DXF done with SolidWorks (saved as R12) ; in CB V1.0 I get 6 lines and 2 arcs, and no problem with snappy (with all snap options enabled)

Can you share your DXF ?

++
David

[Dragonfly]

Update.
I should have examined more deeply. It's not the lines and arcs. There is something else. If I delete the layer the snapping works OK on the rest of the geometry.
I am attaching the offending file. Could not find why this happens. There seems to be an object which causes "Object reference not set to an instance of an object" message to appear when converting to polylines.
Maybe it's an odd case of a damaged object. In which case I apologize for the inconvenience.

[dh42]

Text(230) is empty

delete it or add a text in the TEXT property.

++
David

[Dragonfly]

In this particular case the layer contains only text and dimensions and can be disregarded as a whole. But now I got curious what object is wrong.
I think I found it - Text(230) has object extremas NaN, NaN.
Deleting it stops the error message.
Maybe a check for valid size needed but I guess it will put even more load on the processor.
But if not someone else does it I'll try a script to check for invalid sized objects when I have some spare time.

[Dragonfly]

Wow, David.
You were much faster than me  

[Bubba]

Wow, David.
You were much faster than me  

That's why I call him "Fast David"