Keyboard switch.

cvp

@shinya.ta put a # before the line nextSet... as here-after

if (x+d+dd) > w:
            x = dd
            y = y + d + dd
    vv.frame = (0,0,w,h)
    vv_array.append(vv)

i_set = 0
#nextSet(vv_array[n_sets-1]['nextSet'])  # display 1st setet)

v.present('sheet')
tv.selected_range = (0,0)
tv.begin_editing()```

shinya.ta

@cvp

vv.frame = (0,0,w,h)...

There is an error here.

cvp

@shinya.ta Sorry but without the code, no help possible

cvp

Please post your new 10 last lines

shinya.ta

@cvp

if (x+d+dd) > w:
            x = dd
            y = y + d + dd
    vv.frame = (0,0,w,h)
    vv_array.append(vv)

i_set = 0
#nextSet(vv_array[n_sets-1]['nextSet'])  # display 1st setet)

v.present('sheet')
tv.selected_range = (0,0)
tv.begin_editing()```

    if (y+d+dd) > h:
        h = y + d + dd
    vv.add_subview(b)
    x = x + d + dd
    if (x+d+dd) > w:
        x = dd
        y = y + d + dd
vv.frame = (0,0,w,h)
vv_array.append(vv)

i_set = 0
nextSet(vv_array[n_sets-1]['nextSet']) # display 1st setet)

v.present('sheet')
tv.selected_range = (0,0)
tv.begin_editing()

Insert Code Here

shinya.ta

@cvp

The "indentation error" will appear.

Olaf

The error results from your lines not being well-aligned
Unindenting the x=... and y=... lines should fix it

shinya.ta

@cvp

I'm sorry. The second code is wrong.

shinya.ta

@Olaf

I'm a beginner, so I don't know which line I should go.

cvp

@shinya.ta your modified code is here

shinya.ta

@cvp

I can't use the existing keyboard because it is hidden.
There is no change between the beginning and the change.

cvp

@shinya.ta It's sure that there is a modification between beginning and this last script...
The 4th one before end of script is commented to use the standard keyboard

Or I don't understand your request, in this case, sorry

shinya.ta

@cvp

Can I use this script only in the frame of the keyboard?
Do I need to change my size?

cvp

@shinya.ta Sorry, I don't understand what you want to do. In your initial post, you asked to use standard keyboard instead of the customized one with emojis. Thus, the solution was to not use setInputAccessoryView, thus to comment the line that does this process...

Or, I really don't understand anything.