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

Incorrect behavior of Eraser Tool in Vector Level. #2302

Open
beeheemooth opened this issue Sep 26, 2018 · 3 comments
Open

Incorrect behavior of Eraser Tool in Vector Level. #2302

beeheemooth opened this issue Sep 26, 2018 · 3 comments

Comments

@beeheemooth
Copy link

Issue Summary

There are times when the Eraser Tool behaves strangely: it erases the lines not where it's needed, but elsewhere. Usually this happens when the fill disappears in a mysterious way.

Screenshot or Video Reference

ezgif-1-53d8c8c4e9

Steps to Reproduce

To reproduce this problem, you should be "lucky". Usually, the fill disappears at the places where the vectors forming the closed region intersect, but are several different lines. Most often, the fill disappears when editing vectors. Disappearance of the fill is a common problem, but it is only the tip of the iceberg. The algorithm that calculates the Gap Check lines often produces the following result:
ezgif-1-f5a9ac255d
The Gap Check line will change if you add points.

If you try to erase the line in this case, the erasure will occur in another place, where the Gap Check line leads.
ezgif-1-006bc7a350

System Information

  • OpenToonz Version: all
  • Operating System: Windows 8.1
@RodneyBaker
Copy link
Collaborator

Two year anniversary of this report.
It's not entirely clear how to proceed here other than to suggest users try not to be 'lucky'. :)

@beeheemooth
Copy link
Author

Well, let's sing "happy birthday" for now

@RodneyBaker
Copy link
Collaborator

Conducting review of open requests/issues...
Recommend the observations of this report be included in a review of the Eraser Tool in v1.8 development cycle with a goal to document any incorrect behavior observed; and as relates to this report, especially during use of vector levels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants