HUD moves to accomodate keyboard

[MendyK]

Until now the HUD would stay in the center of the screen, even when the keyboard was up.

My implementation makes it so that if the keyboard is up and HUD.flash() is called, the HUD moves to the center between the keyboard and the top of the container view.
if the HUD is on screen when the keyboard is popping up or down, the HUD will animate up and down in order to not block the keyboard.

[MendyK]

Unit tests are passing. I'm not sure why the travis build is failing.

[PGLongo]

Hi @MendyK and thanks for the PR. Can you add a screenshot and put an example in the demo project?

Don't worry about Travis, unfortunately there is a bug on Travis and some builds sometimes (very often) fail without any reason

[MendyK]

@PGLongo I didn't want to change the current demo, so I made a new demo target. Is that okay?

[MendyK]

Here are the screenshots

[PGLongo]

Please don't add a new demo target. Add an hidden textfield and a new button in the actual target

[PGLongo]

There are two little problem with your implementation:

1. If I don't want to move the HUD? IF I only want to show on top of the keyboard?
2. If i change your demo code as follow your code doesn't work

 override func viewDidLoad() {
        super.viewDidLoad()
       // HUD.dimsBackground = false
        //HUD.allowsInteraction = true
    }

You can easily fix this two issue moving the registerForKeyboardNotifications outside the common init and force the user to register and then unregister

[MendyK]

What do you mean by "force the user to register and then unregister"?

[PGLongo]

Call something like PKHUD. registerForKeyboardNotifications only if you are interested in handling the keyboard

[MendyK]

@PGLongo I also got rid of the keyboard demo target and added a hidden textfield to the demo project as you suggested

[MendyK]

[MendyK]

@PGLongo Is there anything else I can do?

[PGLongo]

Sorry for the delay @MendyK. Unfortunately I need more time for review and tests. I will try to merge this PR in the next two weeks

[PGLongo]

@MendyK I'm deeply sorry for the delay. If you fix the conflict I will test and merge this PR.

Thanks

[MendyK]

@PGLongo Sorry for the delay on my end. I fixed the conflict

[alexookah]

what happened to this pull request? can this still be merged?

[alexookah]

@PGLongo this pull request can now be closed.