-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
f: material designflutter/packages/flutter/material repository.flutter/packages/flutter/material repository.found in release: 3.3Found to occur in 3.3Found to occur in 3.3found in release: 3.6Found to occur in 3.6Found to occur in 3.6frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer version
Description
Hi,
After the last update of Flutter 1.22.2 • 2020-10-16 the new types of buttons have emerged that will give way to the old types.
I noticed that we now have new properties for the ButtonStyle, but I can no longer control the edges of the buttons.
My question is: It is really no longer possible to control the edges of the buttons or I am not knowing how to use the new properties.
In the past we could put a shape: Border, but now the shape properties are of the type: MaterialStateProperty.all which does not allow Border ().
We also have the side property of type: MaterialStateProperty.all which also does not allow Border ().
Remembering that I only want a button with a Border: Top and Bottom.
Has anyone ever experienced this?
Thank you.
Metadata
Metadata
Assignees
Labels
f: material designflutter/packages/flutter/material repository.flutter/packages/flutter/material repository.found in release: 3.3Found to occur in 3.3Found to occur in 3.3found in release: 3.6Found to occur in 3.6Found to occur in 3.6frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer version