Good point about this only getting called when keyboard is first shown. Ideally, you would attach textfield did_begin_editing delegates that scroll the textfield to the top of the scroll view. Even if you don't own those, you could basically store the original delegate within your custom delegate, and then call the original delegate methods after you scroll into place.

Hi!

I'm the guy who asked https://forum.omz-software.com/topic/4930/use-the-numeric-keyboard-easily

I have posted there how to change the type of keyboard using the UI Designer. It's super easy (once you know how to do it. I had to ask Ole).

I hope it helps.

Javier

@cvp thank you for the link

@JonB Thank you very much. callend_editing() method solves my problem perfectly

@procryon , if you look at one of my code examples in this thread you see the delegate being used as @JonB pointed out.
You can see the TextFields Delegate Documentation here

This seems to be caused by iOS 10.3, I'm looking into it.

Did you ever figure anything out?

This question has been solved here. Thanks @JonB for giving me very helpful hint ☺️

@scj643 if you want to take a look how it is implemented go right ahead and add it to objc_tools library. A lot of my implementation came from @jonb

Thanks @jonb this working now.

@ahenry91 I'd really love to see enough keyboard shortcuts in Pythonista that the editor, with a bluetooth keyboard, could be navigated entirely by keyboard shortcuts, without ever touching the screen.

A more complete set of key commands wouldn't be hard for @omz to implement, I guess it's just not a top priority. Anywho, this is something I'd like to see in the next update after Pythonista 3.

Bummer. I sat on iOS 7 forever and finally gave into upgrading when I saw you released the 2.0 update which required a later iOS, only to have overall functionality and usability reduced due to iOS related bugs. I'm grateful for the new functionality, but I would roll back to the old version if it weren't a pain to revert the os as well.

Any hope of fixing this and the other keyboard input bugs?

Oh, yeah, right, they are restricted by iOS. I don't think it's possible to override this within an app.

I have this behavior too. I don't really care, though, I almost never use forward delete ever on any device.

@omz I would very much like that keyboard app, if you ever get back around to it.

Ok, found a working solution in the MapView objc sample:

Need to use a dummy ui.Button and set the Python click handler function as its "action". Then can use the button as the target and sel("invokeAction:") as the action when defining the Objc accessory button.