-
Notifications
You must be signed in to change notification settings - Fork 487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CoachMark is getting out of the screen bounds when applied to table view #152
Comments
Hello @M-I-N, the reason you're seeing this awkward behavior is because your tableview spans more than half the screen. (Meaning that the engine get confused as to where to put the coach mark and resort to the default position.) It'll certainly be an improvement to check the space remaining and place the coachmark where there's the most of it. In the meantime, since you've got more space on the top, you can try to force the orientation in |
Hi @ephread , thanks for the quick reply from you. I've tried the approach you suggested (force the orientation so that
coachMark.arrowOrientation = .bottom My Any idea how to deal with |
Meanwhile, the documentation in the
to reflect the actual behavior. |
I did it with coachMark.arrowOrientation = .bottom as well. |
Hi @ephread it would be very helpful if it were possible to place the coachmark above view it is highlighting. For example for a tableview or for any other view, that covers a large area of the screen, the ability to place the coach mark over the view itself would save a lot of trouble. |
@tectonicpie That's a good idea, I'll put that on the roadmap. |
I've made coach marks for several components of my view controller (e.g.
navigationBar
,rightBarButtonItem
,tableView
, a customUIButton
). Other coach marks but the one fortableView
are being shown appropriately inside the screen bounds. What's wrong when using it withtableView
?Screenshots:

I've followed your default style implementation.
Here are some code snippets:
The text was updated successfully, but these errors were encountered: