Losing Entity Snaps
I seem to be having the same problems losing entity snaps during a drawing session as the post by Patrick Sparrman (i.e. 6.1.0006) dated 2005-10-11. For some reason, flyover snapping stops working and objects (lines, intersections, etc.) are not recognized. It seems to start when I zoom to an object. I'm using version 6.2.0021. Double clicking on the ESNAP button on the status bar does not solve the problem. Also, the ESNAP remains grayed out after double clicking. I have to close the drawing and reopen it to solve the problem. The snaps then work (ESNAP button is blackened) for a short time and then the same problem occurs. Somebody please help!! This is not acceptable!
Comments
-
I had a little trouble with that in 6.2.0019 after having a lot more in an earlier V6 incarnation. It seems to have "come good", maybe some files behave better, but without flyover snaps on snapping fades fairly quickly.Lisps containing "osnap" "midpoint" often don't work and also often crash the program, so I have written them out and have absolutely minimal trouble overall.Object Properties toolbar still causes some various problems so I keep it off.Other than that, Trim fades sometimes and copied objects often disappear until a regen.
0 -
As far as to capabilites of myself "programming" theses problems out, I'm handicapped. My programming knowledge of lisps and macros are minimal. I'm at the mercy of the software working correctly. I'm sure that I have some settings incorrect, but that's the purpose of the forum. Others who have encountered the same problems perhaps can relay "setting" adjustments that solve the problem. If adjustments can't solve the problem, BricsCad should make adjustments to the programming that allows us of limited knowledge to simply "adjust" the settings. As a customer, I expect the software to work properly. I'm sure that there is probably an answer somewhere within the settings.
0 -
Sorry, the reference to lisp was to illustrate the problem I did have with snaps, not how to make the program behave better.I don't believe your problem is in an internal setting in Icad, and this version of this CAD program achieves more of what it says it will, with the least failures or crashes, of any I have used.I save often and believe that helps (a legacy from various unstable Autocad versions).Try turning off the Object Properties toolbar.Here's a suggestion which has solved many of my previous problems (no joke) - see if it's as bad with your virus software turned off.
0 -
Your lisp point was taken. Thanks. I've got BricsCad looking at the problem to see if they can see a setting problem. I've used ICad 98 for years without a problem. Sometimes it seems the more you advance , the worse the problems become. Just looking for suggestions in cause BricsCad has no answer. It's just a problem that HAS to be resolved!
0 -
I have problems with osnaps ceasing to function. When this happens, both running osnaps, and manually are non-functional. A reload of the drawing gets it working again.I'm on version 6.0.0012Joe Dunfee
0 -
I have the same problem. Snapping ability will just stop. Regen will sometimes solve the problem. Resetting the snaps will sometimes solve the problem. Typing in the snap mode in front of a mouse click will not solve the problem. Closing and opening the drawing will always solve the problem. It does not seem to be in large drawings only (which I would suspect,) but I have had it happen in very small drawings with only a few objects.
0 -
I can confirm that same thing happens in Bricscad for Linux version 6.0.0019-1.Best regards, Ljubo
0 -
It's clear from the above that snapping can break down in the current version .Such problems are generally easy to fix once we can reproduce them, only they're also hard to track down.We haven't yet been able to reproduce the problem. It would be good to distinguish between some different possible bugs so here is some background on possible causes.- a missing regen: temporary failure to snap because the information it needs is out of date. For example, imagine snap relies on an out of date zoom distance.Then the program will look for snap points in the wrong location. A regen or regenall should fix that. - broken snap that cannot be reset for the rest of the drawing session. This appears to happen, but a number of reports could actually have one of the other causes.- bugs (or user operations) that inadvertently set OSMODE to 0.The system variable OSMODE controls entity snaps.OSMODE=0 means that no snaps are set.OSMODE>16384 means that snaps are set but they are disabled.If you toggle the ESNAP button on the statusbar then this subtracts or adds 16384 to the value of OSMODE.So what actually counts is the value of OSMODE. If the statusbar button does not change when you click on it, then please verify the value of OSMODE by typing it in. Maybe a bug causes OSMODE to become 0 at times, that could be. Then resetting OSMODE is enough to continue work.Alexander Van Heuverzwyn,Bricscad
0 -
This bug is a show-wstopper.I lost very much ime because of this, since so many months.Really Bricscad has to do something about this.such a bug is a reason enough for gearing onto ACLT.Thanks on forward
0 -
I think this has improved a lot. Its not perfect.Today I mostly only loose the pickbox around the cursor.see this post. PICKBOXhttp://www.bricsys.com/protected/en_INTL/support/forumthread.jsp?id=6710
0 -
I have recently started to evaluate V9 and I see this problem frequently. Even with a very simple drawing, entity snapping just ceases to work. This is a real show stopper. I found this thread in the forum but the posts relate to older versions. Is anyone else having this problem w/ V9. Any fix?
0 -
Recently the flyover snap marker sometimes stops showing, or shows near the place but not on it.It seems to happen most with Perp and Cen, Perp generally works or maybe nudging the mouse wheel makes the marker show.Cen sometimes will not work. If I create a polygon from lines Cen will not work unless I Flatten the polygon, even though the lines had 0 Z-value and so does the polygon. Circles, I sometimes leave the program and start again which is a pain.I can't remember which version of V9 this showed up in, but it is fairly infrequent and too random to make a good report to Support. I think it happnes less in smaller files.I am having a problem with fading Lisps and I think it happens along with the disappearing snaps.
0 -
I have the same problem with V7.My observations are :If I manipulate the "osmode" variable in a lisp program and Iexite the program (i.e. not terminating it properly), Iwill loose the esnaps and nothing will bring them back unlessI restart Bricscad. And yes, this happens in spite of the error-catching routine I'm using, which should reset the values of selected variables to as they were before the programm was started. Every other selected variable is properly reset, but the osnap is lost for good. It's a bit of a nuisance.
0 -
I believe that might be a different problem.I have a lisp (or two) which temorarily sets osnaps to nil, then resets it to previous after picking a couple of points without snap. If I interrupt it part way through, osnap remains at nil or zero. I can reset it using a lisp I have which issues the Distance command after setting osnap to ("osmode" 127) which I find most useful. I use F12 to issue this lisp.With the fading snap syndrome, nothing can make it pick say "Cen", however the snap, esnap or osnap is set.
0 -
I just started testing V9.2.15, and found this bug pretty quickly. Actually I've lived with it for several versions myself. I never could figure what was causing it until today. The PAN command is causing the osnap's to reset. Doesn't matter how it's executed - _PAN, -PAN, PAN, or using the keyboard arrow keys, the osnaps reset. Doesn't happen with RTPAN or RTZOOM. I've installed on two computers, with the same results, so it's not computer specific. I'm going to post a bug report for this.I've only been testing a couple of days, and I've run into a couple of glitches. This is probably the most annoying. At least this version is usable, as opposed to V8.
0 -
That's resetting snaps rather than snaps not working however they are set.I don't Pan very often and have not had snap settings change themselves.However, because there is perhaps more than one problem or more than one symptom, it might be related - sometimes bumping the mouse wheel gets mine working (but not always).I don't recall V8 displaying the snap problem I have now.
0 -
I can verify that executing a pan resets entity snaps as well. I never made the connection before, but it definitely happens often enough to be really annoying. i have had a number of complaints about this very problem since updating to latest V9 version.
0 -
I did post my findings with Tech Support, and they have confirmed there is a problem. They said a fix will be coming soon. Maybe they will take care of the other OSNAP problems that have been reported on this post.
0 -
I just tried panning in a small file, a large one, during a command or not, from the command line... Osnaps always shut down during the pan command (which is a good thing) and reset after the pan is finished. Maybe the ability to reset fades, but I can't make it happen on cue.I generally have osmode set at 127.
0 -
Indeed, in some occasions (e.g. when choosing one of the options instead of picking points), the PAN command failed to restore the OSNAP settings. This is now fixed, the fix will be included in the next update, which will be released in the following weeks.
0