-
Notifications
You must be signed in to change notification settings - Fork 461
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
shapeBorder need to be more customisable #166
Comments
Thanks for your suggestion, we will check out the possible implementation and will update the status over here. |
@vatsaltanna Thanks for considering! Hope it is practicable. |
@ZahraVe Have you tried RoundedRectangleBorder? it can provide the same as your expected output. Ex:
|
@vatsaltanna Oh, yes, I did. It is not working. I looked through the package and saw that in the 'ShapePainter' Class, the radius is forced to be 3.0 if it is not circular (final radius = shapeBorder == CircleBorder() ? 50.0 : 3.0;) I assume that is the reason 'RoundedRectangleBorder' does not work. |
Can you please share a snippet of your code? as I tried with example and it works perfectly. |
@vatsaltanna I tried that on different parts of my work, for different showcases but does not work. BTW, I am assuming you have tried Radius.circular(30) or (40) as well, since the Radius.circular(4) is not any different from 3.0. here is one of them that I want to be rounded border.
|
I guess you catch it right as it was 4 so I got the expected result, we will try to implement possible solutions and will update here. |
✨ Closes #166 shapeBorder need to be more customisable
ShowCaseView is a great package, but it lacks a simple still necessary functionality that you cannot set the 'shapeBorder' to be the same shape as the widget you use it for. For example, in one case, I want the showcase shape to be rectangular with a BorderRadius of 20 in another case with BorderRadius of 40. The package offers only two options for 'shapeBorder' (circular/rectangular with a pre-defined BorderRadius). Would you please add this functionality as well?
The text was updated successfully, but these errors were encountered: