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

rive-flutter does not respect the specified ‘Fills and Strokes’ order #445

Open
k1zerX opened this issue Dec 25, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@k1zerX
Copy link

k1zerX commented Dec 25, 2024

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:

  1. Set up a stroke with a fill atop of it for rectangle in Rive editor
  2. Run Flutter app with this component
  3. Compare thickness of the rendered stroke in Rive editor and Flutter app
  4. 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

Source .riv/.rev file

test.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

And how it actually looks in Flutter app
simulator_screenshot

Device & Versions

  • Device: iOS Simulator
  • OS: iOS 17.5
  • Flutter Version:
Flutter 3.27.1 • channel stable • https://github.com/flutter/flutter
Framework • revision 17025dd882 (9 days ago) • 2024-12-17 03:23:09 +0900
Engine • revision cb4b5fff73
Tools • Dart 3.6.0 • DevTools 2.40.2
@k1zerX k1zerX added the bug Something isn't working label Dec 25, 2024
@HayesGordon
Copy link
Contributor

@k1zerX thanks for reporting, we'll get this resolved soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants