jsketcher
jsketcher copied to clipboard
Constraints stop working.
Hi,
I don't know how this happens exactly, but at some point while editing a sketch in the dedicated sketch view, the constraints stopped working (as in they still exist, but they are ignored when moving sketch points around with the mouse)
I'll edit this post with more info if I replicate this issue, intentionally or accidentally.
EDIT: this definitively seems to be caused by improperly using a named dimension. An exception must be aborting the solver code if there is any unrecognized constraint. Ideally, only the problematic constraint should be disabled, instead of the whole solver.
Are you using a build from the latest master branch? If so it is currently broken in the master branch and I am fixing it.
On Thu, Apr 30, 2020, 10:02 PM z26 [email protected] wrote:
Hi,
I don't know how this happens exactly, but at some point while editing a sketch in the dedicated sketch view, the constraints stopped working (as in they still exist, but they are ignored when moving sketch points around with the mouse)
I'll edit this post with more info if I replicate this issue, intentionally or accidentally.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/xibyte/jsketcher/issues/99, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAENWB42FDPVUZBW6T5ASI3RPJJVDANCNFSM4MW3R4JQ .
I'm going to the the web-cad.org website by typing the url, so I assume so? (If you do rolling releases there)
The web-cad.org is periodically updated. There is a bunch of UI stuff and bug fixes happening now so it will be updated after the master branch is in a good state. See #96 for when this happens.
@z26 This is a very old issue. Could you confirm this is still a problem or not? Seeing if we can close this one.
It's been quite long so I don't remember the exact steps I took back then, but i am unable to recreate this issue.
While investigating this, I did find that setting a distance constraint to A then writing something wrong on purpose like "A = x" (if x doesnt exist) will cause the app to become somewhat but not fully unresponsive. Not a serious problem (the situation is recoverable by deleting the offending statement) but might as well mention it regardless.
I used the 2d sketcher to test this, not the full app.
Ok. Closing this one for now. If you are able to replicate go ahead and create a new issue.