-
Notifications
You must be signed in to change notification settings - Fork 492
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
Cant handle frame changes for the current coachmark #287
Comments
Hey @diegodossantos95, thanks for reporting the issue! I think the README hasn't been updated, let me have a look. |
@ephread What is the right approach to update the Coachmark? |
@diegodossantos95 your current approach sounds correct, but I need to know more about your flow.
|
@ephread , the keyboard is always visible because the coach mark appears on the keyboard's toolbar. The keyboard's size changes when the user changes the keyboard layout, and I listen to this event to update the coachmark's highlight frame. |
@diegodossantos95 alright, thanks for the clarification, IIRC |
@ephread do you mean |
@diegodossantos95 I meant in the delegate's method (see here and there). Sorry, I should I been clearer. |
I tried, but it crashed because of simultaneous access of |
|
Describe the bug
I have a coachmark on top of the keyboard, so I want to change the coachmark position based on the keyboard size.
The issue is that the readme says that we should use the CoachMarkController.prepareForChange() and CoachMarkController.restoreAfterChangeDidComplete(), but those functions don't do anything on iOS 13 or later.
I found a possible workaround, which is to run
flow.pause()
.helper.updateCurrentCoachMark()
,flow.resume()
, but the resume function creates a new coachmark in the screen, so every frame change a new coachmark appears, and keeps the old ones visible.To Reproduce
prepareForChange
function before changing the framerestoreAfterChangeDidComplete
functionExpected behavior
The coachmark should move to the new frame position.
Screenshots
The result of the workaround usage.
Environment
The text was updated successfully, but these errors were encountered: