Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"ok" is not always okay #201

Closed
wants to merge 2 commits into from

Conversation

wpwrak
Copy link
Contributor

@wpwrak wpwrak commented Feb 12, 2017

A sketch may contain errors that cause later groups to fail, but the group list still says that everything is "ok". Here is an example:

not-okay.zip

g004-extrude is based on the outline in g003-sk-outline, which in turn uses geometry from g002-sk-bad-influence.

  • select g002-sk-bad-influence, change c00a-pt-pt-distance to REF, drag the right point to the left of the left point.
  • activate g004-extrude. The extrusion is now a mess, because g003 has become self-intersecting. But the group list still shows a reassuringly green "ok".

With this commit, the "ok" of a group containing a sketch with problems will be shown in yellow:
not-ok-example

Note that this commit touches the same area a my previous DOF indication changed. Since each makes the color selection a little more complicated, I disentangled it here.

Addendum: the "ok" may not turn yellow immediate. E.g., in the above example, it remains green until the group is recalculated, which doesn't happen automatically/immediately in this case.

If a sketch has a "minor" problem, such as being self-intersecting,
this can cause considerably confusion in subsequent groups, yet is
not indicated in the group list.

This commit makes the "ok" yellow in such cases. Note that the
indication may not change immediately when a change leading to
trouble is made, since the dependent groups are not recalculated
on all changes.
@whitequark
Copy link
Contributor

@wpwrak Change looks good to me. Can you please rebase on master?

@whitequark
Copy link
Contributor

@wpwrak ping

@whitequark
Copy link
Contributor

I went ahead and merged this manually, with minor changes.

@whitequark whitequark closed this May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants