great sounds like you "got it". :thumbup:
On the otherhand, I suppose I worded that description kinda vaguely considering how easy the procedure for a successful lasso solve:
If you want to use the fast option predicatably on other component types:
select a majority of the component's area "within" the lasso bounds than is "without" to result in a successfully selection.
But if anyone else did not get it. Consider Maze's lasso example where his "tiny" lasso selection area results in a failure to select all the edges circled with the lasso. ( because the default preference for the lasso is "fast" calculation for better interactivity )
However, I only mention the "accurate" setting to cover all the bases.
You do not have to choose this slower "accurate" option if you circle the majority of a component's screen space. Like so:
If the lassoed area circled over 60% of the same edge's space onscreen... you would then have predictable results. Without having to sacrifice the interactive speed the "fast" setting affords you.
Replies
On the otherhand, I suppose I worded that description kinda vaguely considering how easy the procedure for a successful lasso solve:
But if anyone else did not get it. Consider Maze's lasso example where his "tiny" lasso selection area results in a failure to select all the edges circled with the lasso. ( because the default preference for the lasso is "fast" calculation for better interactivity )
However, I only mention the "accurate" setting to cover all the bases.
You do not have to choose this slower "accurate" option if you circle the majority of a component's screen space. Like so:
If the lassoed area circled over 60% of the same edge's space onscreen... you would then have predictable results. Without having to sacrifice the interactive speed the "fast" setting affords you.