I have Xcode 8 and trying to convert my project to Swift 3.

In my Podfile: pod 'EasyTipView', '~> 1.0.2'

When I build the project, I get:

“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

What am I doing wrong?

I expected easyTipViewDidDismiss to be called when doing self.tipView.dismiss() but it isn't.

I do that when the user taps an overlay. easyTipViewDidDismiss is called when the user taps the tipView (so the delegate should be correct).

Is it an issue or am I holding it wrong?

Updated for Xcode 10.2, Swift 5

Added 1024x1024 Sample App AppStore AppIcon (quiets compiler warning)

NOTE: This will fail CI, unless/until you set up your CI to use XCode 10.2

I have an app with navigationBar and tabBar. What I want is to dismiss EasyTipView when user clicks anywhere outside of the tip. How can it be implemented?

Hi. With the recent addition of Swift Package Manager to Xcode, I was wondering if there is any chance that support for it is added to this awesome library.

Code to reproduce this issue:

var tipPreferences = EasyTipView.globalPreferences
tipPreferences.drawing.arrowPosition = .bottom
tipPreferences.positioning.bubbleVInset = 14
let contentView = MyCustomTipContent()
EasyTipView.show(animated: true, forView: tipViewSource, withinSuperview: view, contentView: contentView, preferences: tipPreferences)

After the tip is presented, I would expect contentView.frame.origin.y to be 14 so that it's fully within the drawn bubble, but instead the y origin is 0 and the content is drawn partially outside (specifically above) the bubble.

It appears that this is an issue of the order in which EasyTipView sets the frame of the content view and when it adds the content view as a subview. The frame is set in arrange(withinSuperview:) and then it's added as a subview in draw(_:). For some reason the addSubview(_:) call causes the frame origin to reset to (0, 0) next time the view is laid out.

I've addressed this somewhat crudely in my own fork of this library: in draw(_:), directly after addSubview(_:) I call layoutIfNeeded to immediately force the frame origin reset. Then I manually set the frame. https://github.com/jaltreuter/EasyTipView/commit/ec165127080a39bcb770165658376bd838fb4a8f

If my commit seems clean enough I can submit it as a pull request, but feel free to do your own investigation as it's possible there's a better solution.

I'm having an issue where I can integrate and link EasyTipView via Carthage with no problem, but when I go to produce an ipa for enterprise deployment with bitcode enabled, I'm receiving this error message from the archive exporter:

Failed to verify bitcode in EasyTipView.framework/EasyTipView: error: Cannot extract bundle from /var/folders/p8/hn20mcb936qgc931vmx35tj00000gn/T/XcodeDistPipeline.dHP/Root/Payload/Spoke.app/Framework…

Does anyone have any suggestions for making the ipa tool play nice with EasyTipView and bitcode in this context?

I tried to create tooltip inside tableview cell component, but... the position mess up after tableView is scrolled or reloaded..

is there any solution for this ?

Thank you in advance Nice Library

The EasyTipView/EasyTipView-Swift.h that is being compiled only supports:

@property (nonatomic, strong) UIColor * _Nullable backgroundColor;

- (void)showWithAnimated:(BOOL)animated forItem:(UIBarItem * _Nonnull)item withinSuperView:(UIView * _Nullable)superview;

- (void)showWithAnimated:(BOOL)animated forView:(UIView * _Nonnull)view withinSuperview:(UIView * _Nullable)superview;

- (void)dismissWithCompletion:(void (^ _Nullable)(void))completion;

It's impossible to even set the text or description of the tooltip..

If you are using tooltips on cells in a table view and you add a header dynamically the tooltip will be miss placed. This PR just opens access to the arrange function so that is possible to manually rearrange the tooltip after it was created.

• if dismissWhenTouchingOutside==true display put an invisible overlay on the window that would make the tooltip dismiss touching anywhere in the screen

The tooltip with multiple parent lists doesn't work because the superview always need to be the global screen view. Out hierachy its

Table [
   ACell [
      Collection [
         BCell << Element to set tip view
      ]
   ]
 ]

if we add the tooltip to BCell with the global superview the library don't understand the 'Y' position because the 'Y' position of the view its 0 (The cell its positionate on the 0 'Y' axis). the solution of this its remove the precondition to set the actual ACell as a superview and this cell has the correct 'Y' position. If i remove the precondition "works" because the library takes the vertical axis with his superview but with the horizontal axis to the view.

This library do not support multiple views inception.

I also try::

tooltip?.show(animated: true, forView: BCell, withinSuperview: collection)
tooltip?.show(animated: true, forView: BCell, withinSuperview: ACell) << This works but without the precondition
tooltip?.show(animated: true, forView: BCell, withinSuperview: Table)
tooltip?.show(animated: true, forView: BCell)

The tooltip is designed to include the arrow within its bounds, and the height of the arrow is included in that calculation

The quick fix is to use the configured arrowPosition to determine which dimension should be included, but arrowPosition is optional (.any is a valid option), and the configured arrow position is not always used.

There's no quick fix, but a workaround hack is to add content padding when using the tooltip:

// Compensate for a bug in EasyTipView which adds the height of the "arrow" to the height of the content bubble, which adds padding below the content
// In addition, and related to this, the arrow is included in the overall size of the tooltip, but not added to the overall size of the tooltip (unless it happens to be at the top or bottom, in which case the hard-coded addition of its height works in our favor).
// This is still tricky because when laying out inside of a specific superview, the arrow direction can be changed when the tooltip doesn't fit. Which means our padding hacking here will result in even worse layout problems.
let defaultPadding: CGFloat = 12
switch position {
case .left:
    tipPreferences.positioning.contentInsets = UIEdgeInsets(top: defaultPadding, left: defaultPadding + 4, bottom: defaultPadding - 4, right: defaultPadding)
case .right:
    tipPreferences.positioning.contentInsets = UIEdgeInsets(top: defaultPadding, left: defaultPadding, bottom: defaultPadding - 4, right: defaultPadding + 4)
case .top:
    tipPreferences.positioning.contentInsets = UIEdgeInsets(top: defaultPadding + 4, left: defaultPadding, bottom: defaultPadding - 4, right: defaultPadding)
case .bottom:
    tipPreferences.positioning.contentInsets = UIEdgeInsets(top: defaultPadding, left: defaultPadding, bottom: defaultPadding - 4, right: defaultPadding + 4)
default:
    fatalError("We can't support 'any' position until that bug is fixed")
}

This workaround is incompatible with .any position and will result in broken layout when the arrow position is changed because it doesn't fit (which seems to only be possible when a superview is specified).

The long-term fix could be:

• Move the layout logic such as in arrange(withinSuperview:) out to the other places that need to be aware of the actual arrow position
• Remove the arrow dimension from the tooltip dimensions, so the size of the bubble is the same regardless of the arrow, and then place the arrow outside of those dimensions. That would also allow a tooltip to be displayed without an arrow, which seems like a useful feature.

I have the situation that an textfield is presented via dynamic prototype cell of an table view. In this case calling the EasyTipView.dismiss() function does nothing. I have to tap the tip explicitely to dismiss it.

In opposite, any textfields inside statical table view cells can be dismissed via dismiss() without a problem.

• This PR closes #218 by removing unnecessary excludes, since the base path is already Sources, so none of those paths are being included in the first place.