Results for “CupertinoTextField”
Full-text search across Boring Doc explanations, official documentation pages, the Flutter API index and every indexed version change.
Version changes
- Make sure that a CupertinoTextField doesn't crash in 0x0 environment3.41.0bugfix
Make sure that a CupertinoTextField doesn't crash in 0x0 environment (Framework, by @ahmedsameha1). CupertinoTextField
- Use maxLengthEnforcement instead of maxLengthEnforced2.0.0breaking
replacement for the now-deprecated boolean `maxLengthEnforced` parameter on `TextField`, `TextFormField`, `CupertinoTextField`, and `LengthLimitingTextInputFormatter` classes. The `maxLengthEnforced` parameter was used to decide whether text fields should truncate
- Deprecated API removed after v2.103.0.0removed
after the 2.10 stable release have been removed. TextField MaxLengthEnforcement.enforce MaxLengthEnforcement.none MaxLengthEnforcement.truncateAfterCompositionEnds TextFormField CupertinoTextField VelocityTracker PointerDeviceKind VelocityTracker.kind PointerDeviceKind.touch DayPicker MonthPicker CalendarDatePicker FlatButton RaisedButton OutlineButton TextButton ElevatedButton OutlinedButton