You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that rive-flutter always draws stroke atop of fill
I've attached screenshots with semitransparent fill, so you can see clearly see the difference
With an opaque fill the button looked like its stroke was twice as thick as in the Rive editor, which is quite difficult to notice, but it felt like something was wrong
Steps To Reproduce
Steps to reproduce the behavior:
Set up a stroke with a fill atop of it for rectangle in Rive editor
Run Flutter app with this component
Compare thickness of the rendered stroke in Rive editor and Flutter app
In Rive editor you only see the outer part of the stroke, because fill covers the inner part. In Flutter app you see the entire stroke, because it is rendered atop of fill
Description
It seems that rive-flutter always draws stroke atop of fill
I've attached screenshots with semitransparent fill, so you can see clearly see the difference
With an opaque fill the button looked like its stroke was twice as thick as in the Rive editor, which is quite difficult to notice, but it felt like something was wrong
Steps To Reproduce
Steps to reproduce the behavior:
Source
.riv
/.rev
filetest.rev.zip
Expected behavior
rive-flutter draws fills and strokes in the specified order
Screenshots
Here you can see the stroke with a semitransparent fill atop in Rive editor (the stroke is enlarged for clarity)
![rive_editor_screenshot](https://private-user-images.githubusercontent.com/35379184/398567322-38d73a16-a3ed-45e5-b39d-cd125c1a7b27.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDI2MDksIm5iZiI6MTczOTE0MjMwOSwicGF0aCI6Ii8zNTM3OTE4NC8zOTg1NjczMjItMzhkNzNhMTYtYTNlZC00NWU1LWIzOWQtY2QxMjVjMWE3YjI3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDIzMDUwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTEyMGYwY2MxY2JmM2VkM2YyZmQ5NTA2YTRjMzAyYWVkZjdkYzhmYjRlMWJkZjVhYjBkOGUyNmIyOGM2OTY1NGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.B2e7YHCDMbnVh9Qj_J3HLIHVtbmmj0GwdG8vBJbXqLI)
And how it actually looks in Flutter app
![simulator_screenshot](https://private-user-images.githubusercontent.com/35379184/398567333-b10608bb-db94-4c0e-996c-eb898ac659b7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDI2MDksIm5iZiI6MTczOTE0MjMwOSwicGF0aCI6Ii8zNTM3OTE4NC8zOTg1NjczMzMtYjEwNjA4YmItZGI5NC00YzBlLTk5NmMtZWI4OThhYzY1OWI3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDIzMDUwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQyZDU0YTA2ZDliYTE3MjQwNTg0MjgzODg2NzNhZTI2NjNiMzdkNjhlMzgzOWE4Zjk1ZmUwNWQzZWU3ZDUxMmImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.UYRsFz992T628i9WvPc52XUS4aZPc--ZS9CwYpCu2h4)
Device & Versions
The text was updated successfully, but these errors were encountered: