2015-03-26 13:32:01 +00:00
|
|
|
/**
|
|
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* This source code is licensed under the BSD-style license found in the
|
|
|
|
* LICENSE file in the root directory of this source tree. An additional grant
|
|
|
|
* of patent rights can be found in the PATENTS file in the same directory.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#import "UIView+React.h"
|
|
|
|
|
|
|
|
#import <objc/runtime.h>
|
|
|
|
|
|
|
|
#import "RCTAssert.h"
|
|
|
|
#import "RCTLog.h"
|
2016-03-16 17:17:09 +00:00
|
|
|
#import "RCTShadowView.h"
|
2015-03-26 13:32:01 +00:00
|
|
|
|
|
|
|
@implementation UIView (React)
|
|
|
|
|
|
|
|
- (NSNumber *)reactTag
|
|
|
|
{
|
|
|
|
return objc_getAssociatedObject(self, _cmd);
|
|
|
|
}
|
|
|
|
|
|
|
|
- (void)setReactTag:(NSNumber *)reactTag
|
|
|
|
{
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
objc_setAssociatedObject(self, @selector(reactTag), reactTag, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
|
2015-03-26 13:32:01 +00:00
|
|
|
}
|
|
|
|
|
2016-03-22 17:56:59 +00:00
|
|
|
#if RCT_DEV
|
2016-03-16 17:17:09 +00:00
|
|
|
|
|
|
|
- (RCTShadowView *)_DEBUG_reactShadowView
|
|
|
|
{
|
|
|
|
return objc_getAssociatedObject(self, _cmd);
|
|
|
|
}
|
|
|
|
|
|
|
|
- (void)_DEBUG_setReactShadowView:(RCTShadowView *)shadowView
|
|
|
|
{
|
|
|
|
// Use assign to avoid keeping the shadowView alive it if no longer exists
|
|
|
|
objc_setAssociatedObject(self, @selector(_DEBUG_reactShadowView), shadowView, OBJC_ASSOCIATION_ASSIGN);
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
2015-03-26 13:32:01 +00:00
|
|
|
- (BOOL)isReactRootView
|
|
|
|
{
|
|
|
|
return RCTIsReactRootView(self.reactTag);
|
|
|
|
}
|
|
|
|
|
|
|
|
- (NSNumber *)reactTagAtPoint:(CGPoint)point
|
|
|
|
{
|
|
|
|
UIView *view = [self hitTest:point withEvent:nil];
|
|
|
|
while (view && !view.reactTag) {
|
|
|
|
view = view.superview;
|
|
|
|
}
|
|
|
|
return view.reactTag;
|
|
|
|
}
|
|
|
|
|
2016-06-07 07:08:16 +00:00
|
|
|
- (NSArray<UIView *> *)reactSubviews
|
2015-03-26 13:32:01 +00:00
|
|
|
{
|
2016-06-07 07:08:16 +00:00
|
|
|
return objc_getAssociatedObject(self, _cmd);
|
2015-03-26 13:32:01 +00:00
|
|
|
}
|
|
|
|
|
2016-11-18 22:33:23 +00:00
|
|
|
- (UIView *)reactSuperview
|
|
|
|
{
|
|
|
|
return self.superview;
|
|
|
|
}
|
|
|
|
|
2016-06-07 07:08:16 +00:00
|
|
|
- (void)insertReactSubview:(UIView *)subview atIndex:(NSInteger)atIndex
|
2016-06-06 17:27:36 +00:00
|
|
|
{
|
2016-06-07 07:08:16 +00:00
|
|
|
// We access the associated object directly here in case someone overrides
|
|
|
|
// the `reactSubviews` getter method and returns an immutable array.
|
|
|
|
NSMutableArray *subviews = objc_getAssociatedObject(self, @selector(reactSubviews));
|
|
|
|
if (!subviews) {
|
|
|
|
subviews = [NSMutableArray new];
|
|
|
|
objc_setAssociatedObject(self, @selector(reactSubviews), subviews, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
|
|
|
|
}
|
|
|
|
[subviews insertObject:subview atIndex:atIndex];
|
2016-06-06 23:23:32 +00:00
|
|
|
}
|
|
|
|
|
2016-06-07 07:08:16 +00:00
|
|
|
- (void)removeReactSubview:(UIView *)subview
|
2016-06-06 23:23:32 +00:00
|
|
|
{
|
2016-06-07 07:08:16 +00:00
|
|
|
// We access the associated object directly here in case someone overrides
|
|
|
|
// the `reactSubviews` getter method and returns an immutable array.
|
|
|
|
NSMutableArray *subviews = objc_getAssociatedObject(self, @selector(reactSubviews));
|
|
|
|
[subviews removeObject:subview];
|
|
|
|
[subview removeFromSuperview];
|
|
|
|
}
|
|
|
|
|
2017-02-02 17:51:19 +00:00
|
|
|
- (UIUserInterfaceLayoutDirection)reactLayoutDirection
|
|
|
|
{
|
2017-02-03 23:13:36 +00:00
|
|
|
if ([self respondsToSelector:@selector(semanticContentAttribute)]) {
|
|
|
|
return [UIView userInterfaceLayoutDirectionForSemanticContentAttribute:self.semanticContentAttribute];
|
|
|
|
} else {
|
|
|
|
return [objc_getAssociatedObject(self, @selector(reactLayoutDirection)) integerValue];
|
|
|
|
}
|
2017-02-02 17:51:19 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
- (void)setReactLayoutDirection:(UIUserInterfaceLayoutDirection)layoutDirection
|
|
|
|
{
|
2017-02-03 23:13:36 +00:00
|
|
|
if ([self respondsToSelector:@selector(setSemanticContentAttribute:)]) {
|
|
|
|
self.semanticContentAttribute =
|
|
|
|
layoutDirection == UIUserInterfaceLayoutDirectionLeftToRight ?
|
|
|
|
UISemanticContentAttributeForceLeftToRight :
|
|
|
|
UISemanticContentAttributeForceRightToLeft;
|
|
|
|
} else {
|
|
|
|
objc_setAssociatedObject(self, @selector(reactLayoutDirection), @(layoutDirection), OBJC_ASSOCIATION_RETAIN_NONATOMIC);
|
|
|
|
}
|
2017-02-02 17:51:19 +00:00
|
|
|
}
|
|
|
|
|
2016-06-09 16:48:56 +00:00
|
|
|
- (NSInteger)reactZIndex
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
{
|
2017-05-29 04:35:38 +00:00
|
|
|
return self.layer.zPosition;
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
}
|
|
|
|
|
2016-06-09 16:48:56 +00:00
|
|
|
- (void)setReactZIndex:(NSInteger)reactZIndex
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
{
|
2017-05-29 04:35:38 +00:00
|
|
|
self.layer.zPosition = reactZIndex;
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
}
|
|
|
|
|
2017-05-29 04:35:38 +00:00
|
|
|
- (NSArray<UIView *> *)reactZIndexSortedSubviews
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
{
|
2017-05-29 04:35:38 +00:00
|
|
|
// Check if sorting is required - in most cases it won't be.
|
|
|
|
BOOL sortingRequired = NO;
|
|
|
|
for (UIView *subview in self.subviews) {
|
|
|
|
if (subview.reactZIndex != 0) {
|
|
|
|
sortingRequired = YES;
|
|
|
|
break;
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
}
|
|
|
|
}
|
2017-05-29 04:35:38 +00:00
|
|
|
return sortingRequired ? [self.reactSubviews sortedArrayUsingComparator:^NSComparisonResult(UIView *a, UIView *b) {
|
|
|
|
if (a.reactZIndex > b.reactZIndex) {
|
|
|
|
return NSOrderedDescending;
|
|
|
|
} else {
|
|
|
|
// Ensure sorting is stable by treating equal zIndex as ascending so
|
|
|
|
// that original order is preserved.
|
|
|
|
return NSOrderedAscending;
|
|
|
|
}
|
|
|
|
}] : self.subviews;
|
Implement CSS z-index for iOS
Summary:
This diff implement the CSS z-index for React Native iOS views. We've had numerous pull request for this feature, but they've all attempted to use the `layer.zPosition` property, which is problematic for two reasons:
1. zPosition only affects rendering order, not event processing order. Views with a higher zPosition will appear in front of others in the hierarchy, but won't be the first to receive touch events, and may be blocked by views that are visually behind them.
2. when using a perspective transform matrix, views with a nonzero zPosition will be rendered in a different position due to parallax, which probably isn't desirable.
See https://github.com/facebook/react-native/pull/7825 for further discussion of this problem.
So instead of using `layer.zPosition`, I've implemented this by actually adjusting the order of the subviews within their parent based on the zIndex. This can't be done on the JS side because it would affect layout, which is order-dependent, so I'm doing it inside the view itself.
It works as follows:
1. The `reactSubviews` array is set, whose order matches the order of the JS components and shadowView components, as specified by the UIManager.
2. `didUpdateReactSubviews` is called, which in turn calls `sortedSubviews` (which lazily generates a sorted array of `reactSubviews` by zIndex) and inserts the result into the view.
3. If a subview is added or removed, or the zIndex of any subview is changed, the previous `sortedSubviews` array is cleared and `didUpdateReactSubviews` is called again.
To demonstrate it working, I've modified the UIExplorer example from https://github.com/facebook/react-native/pull/7825
Reviewed By: javache
Differential Revision: D3365717
fbshipit-source-id: b34aa8bfad577bce023f8af5414f9b974aafd8aa
2016-06-07 14:40:25 +00:00
|
|
|
}
|
|
|
|
|
2016-06-07 07:08:16 +00:00
|
|
|
- (void)didUpdateReactSubviews
|
|
|
|
{
|
2017-05-29 04:35:38 +00:00
|
|
|
for (UIView *subview in self.reactSubviews) {
|
2016-06-07 07:08:16 +00:00
|
|
|
[self addSubview:subview];
|
|
|
|
}
|
2015-03-26 13:32:01 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
- (void)reactSetFrame:(CGRect)frame
|
|
|
|
{
|
|
|
|
// These frames are in terms of anchorPoint = topLeft, but internally the
|
|
|
|
// views are anchorPoint = center for easier scale and rotation animations.
|
|
|
|
// Convert the frame so it works with anchorPoint = center.
|
|
|
|
CGPoint position = {CGRectGetMidX(frame), CGRectGetMidY(frame)};
|
|
|
|
CGRect bounds = {CGPointZero, frame.size};
|
|
|
|
|
|
|
|
// Avoid crashes due to nan coords
|
|
|
|
if (isnan(position.x) || isnan(position.y) ||
|
|
|
|
isnan(bounds.origin.x) || isnan(bounds.origin.y) ||
|
|
|
|
isnan(bounds.size.width) || isnan(bounds.size.height)) {
|
|
|
|
RCTLogError(@"Invalid layout for (%@)%@. position: %@. bounds: %@",
|
|
|
|
self.reactTag, self, NSStringFromCGPoint(position), NSStringFromCGRect(bounds));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2015-10-23 16:11:54 +00:00
|
|
|
self.center = position;
|
|
|
|
self.bounds = bounds;
|
2015-03-26 13:32:01 +00:00
|
|
|
}
|
|
|
|
|
2016-01-15 13:14:27 +00:00
|
|
|
- (void)reactSetInheritedBackgroundColor:(__unused UIColor *)inheritedBackgroundColor
|
2015-05-28 16:29:27 +00:00
|
|
|
{
|
Disable background color propagation for everything except text nodes
Summary:
public
Blending semitransparent pixels against their background is fairly a fairly expensive operation on mobile GPUs. To reduce blending, React Native has a system called "background color propagation", where the background color of parent views is automatically inherited by child views unless explicitly overridden. This means that translucent pixels can be blended directly against a known background color, avoiding the need to do this dynamically on the GPU.
In practice, this is only useful for views that do their own drawing, which is basically just `<Image/>` and `<Text/>` components, and for image components it only really matters when the image has an alpha component.
The automatic background propagation is a bit of a hack, and often does the wrong thing - for example if a view overflows its bounds, or if it overlaps a sibling, the background color will often be incorrect and need to be manually disabled. Because the only place that it provides a significant performance benefit is for text, this diff disables the behavior for everything except `<Text/>` nodes. It might still be useful for `<Image/>` nodes too, but looking through the examples in UIExplorer, the number of places where it does the wrong thing for images outnumbers the cases where it provides significant reduction in blending.
Note that this diff does not prevent you from eliminating blending on image components by manually setting an opaque background color, nor does it stop you from disabling color propagation on text components by manually setting a transparent background.
Reviewed By: javache
Differential Revision: D2811031
fb-gh-sync-id: 2eb08918c9031c582a3dd2d40e04b27a663dac82
2016-01-08 11:37:25 +00:00
|
|
|
// Does nothing by default
|
2015-05-28 16:29:27 +00:00
|
|
|
}
|
|
|
|
|
2015-07-31 18:23:29 +00:00
|
|
|
- (UIViewController *)reactViewController
|
2015-03-26 13:32:01 +00:00
|
|
|
{
|
|
|
|
id responder = [self nextResponder];
|
2015-06-24 17:14:37 +00:00
|
|
|
while (responder) {
|
|
|
|
if ([responder isKindOfClass:[UIViewController class]]) {
|
|
|
|
return responder;
|
|
|
|
}
|
|
|
|
responder = [responder nextResponder];
|
2015-03-26 13:32:01 +00:00
|
|
|
}
|
|
|
|
return nil;
|
|
|
|
}
|
|
|
|
|
2015-07-31 18:23:29 +00:00
|
|
|
- (void)reactAddControllerToClosestParent:(UIViewController *)controller
|
2015-03-26 13:32:01 +00:00
|
|
|
{
|
|
|
|
if (!controller.parentViewController) {
|
|
|
|
UIView *parentView = (UIView *)self.reactSuperview;
|
|
|
|
while (parentView) {
|
2015-07-31 18:23:29 +00:00
|
|
|
if (parentView.reactViewController) {
|
|
|
|
[parentView.reactViewController addChildViewController:controller];
|
|
|
|
[controller didMoveToParentViewController:parentView.reactViewController];
|
2015-03-26 13:32:01 +00:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
parentView = (UIView *)parentView.reactSuperview;
|
|
|
|
}
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-04-03 22:11:02 +00:00
|
|
|
/**
|
|
|
|
* Focus manipulation.
|
|
|
|
*/
|
|
|
|
- (BOOL)reactIsFocusNeeded
|
|
|
|
{
|
|
|
|
return [(NSNumber *)objc_getAssociatedObject(self, @selector(reactIsFocusNeeded)) boolValue];
|
|
|
|
}
|
|
|
|
|
|
|
|
- (void)setReactIsFocusNeeded:(BOOL)isFocusNeeded
|
|
|
|
{
|
|
|
|
objc_setAssociatedObject(self, @selector(reactIsFocusNeeded), @(isFocusNeeded), OBJC_ASSOCIATION_RETAIN_NONATOMIC);
|
|
|
|
}
|
|
|
|
|
|
|
|
- (void)reactFocus {
|
|
|
|
if (![self becomeFirstResponder]) {
|
|
|
|
self.reactIsFocusNeeded = YES;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
- (void)reactFocusIfNeeded {
|
|
|
|
if (self.reactIsFocusNeeded) {
|
|
|
|
if ([self becomeFirstResponder]) {
|
|
|
|
self.reactIsFocusNeeded = NO;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
- (void)reactBlur {
|
|
|
|
[self resignFirstResponder];
|
|
|
|
}
|
|
|
|
|
2017-05-29 22:56:42 +00:00
|
|
|
#pragma mark - Layout
|
|
|
|
|
|
|
|
- (UIEdgeInsets)reactBorderInsets
|
|
|
|
{
|
|
|
|
CGFloat borderWidth = self.layer.borderWidth;
|
|
|
|
return UIEdgeInsetsMake(borderWidth, borderWidth, borderWidth, borderWidth);
|
|
|
|
}
|
|
|
|
|
|
|
|
- (UIEdgeInsets)reactPaddingInsets
|
|
|
|
{
|
|
|
|
return UIEdgeInsetsZero;
|
|
|
|
}
|
|
|
|
|
|
|
|
- (UIEdgeInsets)reactCompoundInsets
|
|
|
|
{
|
|
|
|
UIEdgeInsets borderInsets = self.reactBorderInsets;
|
|
|
|
UIEdgeInsets paddingInsets = self.reactPaddingInsets;
|
|
|
|
|
|
|
|
return UIEdgeInsetsMake(
|
|
|
|
borderInsets.top + paddingInsets.top,
|
|
|
|
borderInsets.left + paddingInsets.left,
|
|
|
|
borderInsets.bottom + paddingInsets.bottom,
|
|
|
|
borderInsets.right + paddingInsets.right
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
|
|
|
- (CGRect)reactContentFrame
|
|
|
|
{
|
|
|
|
return UIEdgeInsetsInsetRect(self.bounds, self.reactCompoundInsets);
|
|
|
|
}
|
|
|
|
|
2015-03-26 13:32:01 +00:00
|
|
|
@end
|