@JonB said:

For doing 1:1 character replacements, maketrans plus translate makes for clean code. You list all the characters you are replacing in one string, all the replacements in the second, and all the characters to delete in the third argument to maketrans.

Damn, I never knew about this. Now I can finally replace my for c in (...): s = s.replace(c, "") loops. My code may finally look acceptable.

Well everyone has or had this issue in past, but we are here to get the solution, so can we have that, please.

in kivy it is solved this way:

from kivy.core.window import Window Window.softinput_mode = ‘below_target’ ``

You can test the ios font and their glyphs with a short script:

from objc_util import * UIFont = ObjCClass('UIFont') vObjCAllFontNames = [] vObjCFontFamilieNames = UIFont.familyNames() for vObjCFontFamilieName in vObjCFontFamilieNames: vObjCFontNamesWithinFamily = UIFont.fontNamesForFamilyName_(vObjCFontFamilieName) vObjCAllFontNames += vObjCFontNamesWithinFamily vFontFamilieNames = [] vAllFontNames = [] for vTemp in vObjCFontFamilieNames: vFontFamilieNames.append(str(vTemp)) for vTemp in vObjCAllFontNames: vAllFontNames.append(str(vTemp)) vAllFontNames.sort() for vFont in vAllFontNames: vConsoleFont = [(vFont, 20), (0, 0, 0)] console.set_font(vConsoleFont[0][0], vConsoleFont[0][1]) console.set_color(vConsoleFont[1][0], vConsoleFont[1][1], vConsoleFont[1][2]) print(vConsoleFont[0][0]) print(u'\u0048\u0065\u006c\u006c\u006f \u0057\u006f\u0072\u006c\u0064\u003a \u10c5\u10c7\u10cd\u10d0\u000a') console.set_font() console.set_color(0.00, 0.00, 0.00)

Maybe this is a help for you, but i didn't test it.
FontInstaller

@omz

Btw thank you for pythonista, it was the one thing that actually got me started with programming and made me realize how much I love it. It’s been my hobby for the last 5 months overtaking my love for video games😂

@shinyformica, gist seems good if it is clear that it is not going to need many revisions, issues, a Readme or collaboration. Otherwise, a git repo is not that much more work.

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?