Perpendicular snap appears when it shouldn't ?
BricsCAD BIM v 26.2.06 FR
Before submitting a bug report, I'd like to make sure the behaviour I'm witnessing is as abnormal as I think.
Context :
- BricsCAD BIM v 26.2.06 FR
- a drawing with only a simple polyline
- only "endpoint" and "perpendicular" snaps active
When I use the "move" command and select the polyline, perpendicular snaps appears when there should only be endpoint ones.
Is this a practical problem ? Yes ! Because, in more complex situation, a user could (been there, done that) click inadvertenly (because it isn't expected to be there) when the perpendicular snap is active, and thus get a slightly wrong base point.
Am I missing something, or is it a bug ?
Joined : a video, and a dwg.
Comments
-
Am I missing something,
It may be to do with how far your zoomed in, normally with a move can see the object, the end worked all the time and then moved perp to other object or an end.
0 -
The end snaps work fine, for the perpendicular snap I would expect it to lock close to where the pickbox is but it locks relatively far from the pickbox location. The latter doesn't make sense to me.
It seems it is locking onto a segment of the dashed line in paper space but that too doesn't make sense as one would expect it to lock to the nearest segment.
You should probably file a support request for this behaviour as this is a bit unpredictable and therefor not desirable.
1 -
Couldn't reproduce it, but as RSW suggests, a service request is appropriate. Even more because combined settings for
OSModethat include_perpare a recipe for surprises. You usedendp(1) andperp(128), equalsOSMode 129. I use511normally and are often surprised byperpgoing to an endpoint or close to an endpoint. Very annoying, just like you illustrated in the video.0 -
If its a problem press Right button mouse, pick perp or just type "perp" this will override the current osnap. You can also use a transparent command say '128 note the single apostrophe, you have a lisp defun pre loaded.
(defun c:128 ()(setvar 'osmode 128)) we had like 5 of these for when osnaps were wrong.
Example Move pickobject pick1stpoint '128 click, then type say 47 which resets your defuns to osnap matching value 47. As per defun above.
0 -
Snaps are a bit of mess in my opinion, I wish the developers would get to spend some serious amount of time and effort to fix it.
- Make the snaps reliable and accurate, especially for drawing views containing 3D objects as it is even worse there than with 2D
- Make the snaps predictable. e.g if one is near the mid point of a line and only end and perpendicular snaps are on, it should automatically go for a perpendicular snap from the first click point and not to an endpoint
- Regarding dimensions… they can lose their associativity to objects even when there is no dimensional change at all. So either the snaps are not reliable/accurate causing the dimension not to be associative at all despite what the properties panel says or there is something wrong with the associativity functionality or both. I seriously consider inaccurate snapping to be a potential cause for that issue, so that brings the issue back to point 1.
This reliability/accuracy issue still not having been fixed after all these years makes it bonkers that one has to spend an inordinate amount of time on checking and fixing misalignment, gaps etc. to get good working hatching and/or reliable dimensioning.
2 -
I know how to use a temporary single snap. But if I have to specify it for every point, it's gonna take several times longer, and I'm gonna get nuts.
0 -
Thanks for the insights. It's something that's been hindering us, and it's difficult to justify to colleagues who keep saying (righly so) that "it doesn't happen in Othercad".
0 -
I've been working with "othercad" for six days in a row last weeks and I can confirm it works flawless (considering object snap). So, yes, I would like to repeat RSW's words:
+++++
Snaps are a bit of mess in my opinion, I wish the developers would
get to spend some serious amount of time and effort to fix it.- Make the snaps reliable and accurate, especially for drawing views containing 3D objects as it is even worse there than with 2D
+++++
0 - Make the snaps reliable and accurate, especially for drawing views containing 3D objects as it is even worse there than with 2D
-
In my experience, PER has always been a problem. Doesn't play well with others. I exclude it from my running osnaps, and use a shortcut key that makes PER an osnap override.
0
