Is there a way to make the buttons center aligned? Right now, all the buttons are on the left (left aligned). People have to move their hands a lot to tap on them on a really wide screen.

I believe this is as simple as it can get. It removes the button having a textField/textView/searchBar property but I don't believe it should be the buttons job to know that. Let me know what you think.

I think the changes I have made simplify the code. In particular button creation. You can now create a button title without subclassing. I have made use of blocks instead of subclassing the button. Let me know what you think.

This adds a buttons property to RFKeyboardToolbar that can be used to change the buttons, and a setButtons:animated: variant that can animate the button changes. The demo is updated accordingly, to add a button for each distinct word in the field.

I have many buttons on my toolbar, when I try to scroll it, I found that I cannot scroll it unless I start my touch on the the little spaces between the buttons, otherwise the button that I touched will be pressed.

Can this somehow be handled? If the gesture is a pan, can the button not be triggered and instead the toolbar will scroll?

Is it possible to hardcode the position of the items in the toolbar?

I'm thinking of something like this:

Dynamic_string_button............................................Bold...Italic... The Dynamic_string_button is used as a sort of pseudo autocorrect based on a prepopulated list of words (appears based on what the user types). Bold and Italic button are used to modify the textView.

If the Dynamic_string_button doesn't match any keywords, then only Bold/Italic is shown, but they are still aligned to the right, so something like:

.....................................................Bold....Italic

I want to use a picture of a slanted "I" as a button on the toolbar, like this:

I can't find any constructors that accept an image, so i tried this:

let italicButton = RFToolbarButton(title: "", andEventHandler: { 
  // function
}, for: .touchUpInside)!
italicButton.setImage(UIImage(named: "italic"), for: .normal)
italicButton.setImage(UIImage(named: "ialic"), for: .highlighted)
textView.inputAccessoryView = RFKeyboardToolbar(buttons: [italicButton])

But the button did not appear on the toolbar.

Hello and thanks for the excellent library. There is a small issue in the example when in the viewdidload method you are calling a non existing method: this:

[RFKeyboardToolbar addToolbarTo:_textView withButtons:@[exampleButton]];

should be:

[RFKeyboardToolbar addToTextView:_textView withButtons:@[exampleButton]];

also on the RFExampleToolbarButton the

[[RFToolbarButton textInput] insertText:@"Example text."];

seems to be an unknown selector

maybe what you wanted to have there is:

 [[RFToolbarButton textView] insertText:@"Example text."];

thanks Konstantinos

Hi! I've been using your library for a couple of years - it's great! I noticed that since Xcode 9, this code causes a warning related to block declaration semantics: This block declaration is not a prototype. The fix appears to be simple. Hope you won't mind accepting this PR!

GitHub changed the way Markdown headings are parsed, so this change fixes it.

See bryant1410/readmesfix for more information.

Tackles bryant1410/readmesfix#1

This may just be my issue, but it appears that the contentInset is not being set initially when adding a lot of buttons, or possible one button (untested).

See this demo screenshot:

You are able to scroll, and when scrolling back, you get the proper contentInset, however, not initially.