* [Button] Add custom font properties
* Add example and tests
* Add sample supporting custom font and dynamic type
* Clean up tests
* Fix C&P error in Copyright date.
* Remove outdated warning
* Fix misuse of standardFont and simplify scale invocation.
"Forcing" wasn't the right phrasing, it only prevents layout updates if "NO".
Using a gerund, "forcing", also doesn't match the style of methods. Gerunds are preferred for
protocols.
Closes#2571
* [Buttons] Improve FloatingButton documentation
* Rename `internalLayoutSpacingInsets` to `internalLayoutInsets`
* Add comments to outline the layout code in the implementation
* Update header documentation to provide more detail about how the new
setters affect layout.
Closes#2566
The previous name, imageTitleSpacing sounds too much like a protocol name,
one that would adjust the space between things.
Amends #2563
Implements #2495
* [Buttons] Remove .largeIcon shape from FloatingButton (#2513)
The LargeIcon shape is not required, since the same behavior (support
for 36-point images) can be achieved by setting the contentEdgeInsets to
.zero.
Also updates one of the button examples to use a 36-point icon.
* [Buttons] Add extended FAB layout code (#2528)
Creating (internal for now) the required properties and layout code to support
the extended FAB. Unit tests to confirm the behavior and some minor
adjustments to existing values like default contentEdgeInsets values.
Implements #2495
* [Buttons] Expose Extended FAB properties (#2543)
Making the new properties public and also migrating away from simple
property setters to the new forShape:inMode: setters required for
UIAppearance support.
* minimumSize
* maximumSize
* contentEdgeInsets
* hitAreaInsets
Implements #2495
* [Buttons] Add basic Floating Button example (#2554)
Includes automatic adjustment of extended/normal layout depending on size
classes.
Demonstrates #2495
* [Buttons] Update README for Extended FAB (#2561)
The README includes usage examples for the FAB. Adding a section to
demonstrate how to configure the FAB in its different shapes and modes.
Documents #2495
* Enable updated ink on MDCButton, add support for shadowPaths
* Only change frame inset when legacy ink is used
* Update formatting
* Create mask layer once
* Update animation and opacity based on designer feedback
* Remove commented animations
* Move constants
* Added warnings to examples.
* fixed some warnings
* using button sender parameter.
* use button sender in example
* use button sender in example
* removed sender from methods that don’t use it.
* removed sender from methods that don’t use it.
* use button sender in example
* use button sender in example
* use button sender in example
* use button sender in example
* Fixed init of header configurator to use passed in parameter
* removed unused API
* use button sender in example
* Revert "Added warnings to examples."
This reverts commit 91f0480f86cb609c47b00f1346f82de67c31c4e9.
* fixed example: Using the view controllers navigationItem rather than creating a new one.
* removed finished checks from animation blocks in examples.
* reverted id sender checks
* revert id sender check for Flexible header UINavigationBar
* revert clug
* revert clug
* addressing nits
* removed sender check for FeatureHighlightTypicalUseView
* more nits
When a button's elevation is assigned, it animates a change to the underlying
shadow elevation. However, this causes animation "jumps" when elevations for
multiple states are being assigned simultaneously. Instead of blindly
assigning the new value to the layer, a check for a change should be performed
instead.
Closes#2483
Buttons should no longer use the subclassing method `-cornerRadius` and
should instead depend on the backing layer's `cornerRadius` property.
Closes#2255
* [Buttons] Restore alpha when re-enabled
When re-enabled, MDCButton previously set its alpha avalue to 1 instead
of the previously-set value.
Closes#1964
* Setting _enabledAlpha in -setAlpha:
The FAB in Typical Use was misaligned, resulting in a blurry image. The
Storyboard and Swift example had misaligned buttons due to
safeAreaInsets on iOS 11.
* [Buttons] Support colored shadows
Adding new method to set a shadow color for each UIControlState.
* Fixing unit test for control state checking
* Fixing some unit tests failing on iPhone 4s/iOS 8.3
* Removing log
* Always initializing _shadowColors, adding unit test for upgrade path
* Fixing white space
* [Buttons] Deprecate subclassing cornerRadius and defaultContentEdgeInsets
* Remove unused import
* Set contentEdgeInsets via UIAppearance
* Content edge insets comment
* Use correct value for FAB hit area insets
* Fix FAB contentEdgeInsets
* [Buttons] Deprecate subclassing cornerRadius and defaultContentEdgeInsets
* Remove unused import
* Set contentEdgeInsets via UIAppearance
* Content edge insets comment
* Use correct value for FAB hit area insets
* Fix FAB contentEdgeInsets
All examples now have at least the required `+catalogBreadcrumbs` and `+catalogIsPrimaryDemo`. All examples in the same breadcrumbs path have only one primary demo. There should be only one `-catalogDescription` attached to the primary demo.
Closes#1897
The Floating Action Button should have default hitAreaInsets so that it
adheres the minimum touch target in the Material Design guidelines.
This commit introduces a set of default hitAreaInsets for the different
FAB styles as well as a warning if a button's touch target is smaller
than the 48-point minimum.
Closes#223
