-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
fabric.PatternBrush difference between drawing mode and resulting fabric.Object #851
Comments
I think I noticed this before as well. Will investigate. |
@kangax Since changing originX/originY to left/top all brushes positioned wrong after mouseUp. You can see it in kitchensink demo. |
Great.... |
Spent couple hours trying to figure this out but without success for now... asked related question on SO. Moving this out of 1.4 for now. |
Are there news for this bug? |
Not from me On Thu, Jan 30, 2014 at 5:53 AM, pstolz notifications@github.com wrote:
|
it think that in renderStroke we are missing the counterpart of this part of renderFill function:
|
Ok i found the problem: When the object is actually created, we always do some translation of canvas to place it properly. I think anyway this is the problem. I was thinking about do the correct translation just in the path _render function, because this problem is tied mainly to drawing mode that produces path, is not a general rule of our rendering pipeline. |
If you draw a
fabric.PatternBrush
the result during the drawing mode is different to to the createdfabric.Path
.You can see this in kitchensink demo - draw one dot (before testing update fabric - see ba2a0e6).
In drawing mode:
After drawing mode (fabric.Path):
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: