Character input

[Yoo Byeng Han]

I am doing most of my work with Ninox.
Tap Forms5 I liked the nice thing about the UI and bought it ….
problem:
1. When adding a record to a field in a linked table: The first character consonant and vowel are solved and input
2. When adding a new record to the pop-over window: If you type a character by pressing the + button, the last character is not entered. (However, if you hit enter,

Current situation: It’s very annoying and I would like to throw the keyboard.
1. Enter a character, press the spacebar once, clear it with backspace again, press enter
2. Write the first character, erase it with backspace, then retype

I believe that there is no problem of Hangul solving except two cases.

Update via Apple Store.

Attachments:

You must be logged in to view attached files.

[Yoo Byeng Han]

2. You can enter it by typing Enter. Sometimes, Hangul is released and the last character is not input.

[Brendan]

Hello Yoo,

I split your post to a new topic because I don’t think your issue has anything to do with Tap Forms 5.3, which is not quite ready for release.

What do you mean by “Hangul”? I’m not familiar with that word.

Do you mean the last cell in the multi-column list view or on a linked table view is not getting the value you entered when you press the return key?

Thanks!

Brendan

[Yoo Byeng Han]

I’m a Korean.

Please let me use Hangul.
File Maker, Ninox, etc. did not have this problem at all.

Attachments:

You must be logged in to view attached files.

[Brendan]

Ah, so Hangul is the Korean writing system.

I’m not sure why it wouldn’t work in Tap Forms. It works with Chinese and Japanese. So it should work with Korean.

In the screenshot on the left with the popover, what is the wrong part? It does look like the one up top is missing a character from the input field below.

[Yoo Byeng Han]

Last character disappear

Please modify the Tap Forms program by referring to the link below
https://github.com/bangjunyoung/KoreanTextMatcher
If you search Google for a neutral Korean moon, you can see why this happens.
As it stands, Tap Forms is very inconvenient to type in Korean, but no one will be using it.

Ninox & File Maker does not experience this problem with default input systems.
However, File Maker Pro says that if you need to write a Script and input in Korean, you can create and solve a user function.

I hope you can enter Korean correctly.

[Brendan]

Hi Yoo,

I wouldn’t be able to integrate that KoreanTextMatcher into Tap Forms because it’s written in Java. Tap Forms is written in Objective-C.

Is the way you enter characters in Korean that much different than Chinese or Japanese? Tap Forms supports Chinese and Japanese localizations and I know I’ve never had any complaints about inputting characters.

Would you be able to make a screencast showing the problem you’re having? It may help me to better understand the issue.

I copied and pasted some text from the PDF document you uploaded and it seemed to have the same characters in the pasted content in Tap Forms.

Thanks,

Brendan

[Yoo Byeng Han]

The phenomenon of the first character being released and the last character being deleted when entering Han-gul.
https://www.dropbox.com/s/c3c2yokfg7ywc8p/Tap%20Forms_Hangul%28korea%29.mp4?dl=0

#.First characterization issue: essentially update from Tap Fprms.
UTF character transformation (unabsorbed, neutral, and longitudinal) is required, and then reassembled and applied as fields.

#.Troubleshoot problems with deleting end characters in File Maker Pro
1.Enter text in field
2. Creating Scripts
if [Code (Get key input trigger ) = 10 Code (Get (key input trigger ) = 13 ]
Perform the script [ “A” ; ]
OnTimer Script Installation [ ; ]
script [text result: 0 ]
End if

3 “A” Script Creation
OnTimer Script Installation []
…

[Yoo Byeng Han]

We rewrote it to help you understand.

#. The first specialization problem: it happens when you press the + button +> By default, you need to update the “tab format” to solve the problem.
Workaround: UTF unicode character conversion is required.
The Primary, neutron, trait waves must be reassembled by separating them into the following fields.

[Brendan]

I see the issue with typing into the Pick List popover where it loses the last character. What if you press the tab key before you click the + button? Does that solve the problem for you?

I copied and pasted some characters from that PDF file you provided and I didn’t see this issue. Maybe it happens only when manually typing on a Korean keyboard. But I don’t have a Korean keyboard and I don’t know how to input those kinds of characters. I could try enabling Korean input.

[Yoo Byeng Han]

The problem of typing Korean in Pick List has been completely resolved.
When tap key, return key, + key, or enter key after typing, the same result was obtained.
I’m quite pleased.

There is still a problem with typing in Hangeul on only one portal.
Select a text field in the portal and type in Korean to release it.
When you click on the text portal once more, Hangul won’t work.
It’s inconvenient to press twice each time.
In a text field other than a portal, the cursor is blinking at the same time as the selection.
Please correct this.

Ver5.3.2 Issue
1. Pressing Create a new record on the portal (+ key) will hide all records in the portal. If you go to another table and come back, you have a problem of showing up properly.

[Brendan]

Hi Yoo,

Can you please make a screen recording of both these issues? It will help me to understand the problem.

Thanks,

Brendan

[Yoo Byeng Han]

Problem: Hangul phenomenon
-.Problems when typing Hangul immediately while the field is selected.

possible: If the completed Hangul input
-. When you use the alphabet or number as the first letter in the field where the field is selected and then input the Hangul
-. When you select a field and press the left mouse button once again,

video
https://www.dropbox.com/s/iv98zkqanx716sf/Hangul%20Input%20problem.mp4?dl=0

[Yoo Byeng Han]

Existing records disappear from portal when wrong relationship setting is made

It was my mistake to set up the relationship (many-to-many, one-to-many, join).
   -. When adding a new record (+ key) according to the relation setting, the existing record disappears …..
     (If you switch to a different layout and come back to the original layout, it will look fine.)

But I can not understand why this is happening.

video
https://www.dropbox.com/s/xp2vscuonpfu8de/potal%20problem.mp4?dl=0

File
https://www.dropbox.com/s/nrbepjl7l6s3yem/potal%20problem.tfarc?dl=0
https://www.dropbox.com/s/d7or69ep0f26afy/potal%20problem.tff?dl=0

[Brendan]

Thanks for the sample file.

If you switch the Link Type, you should then un-check the “Show Inverse Relationship” option and then re-select it.

Right now your Join relationship looks like the inverse of a One-to-Many on your 청구서 내역 form. So on your 청구서 전표 form, go to the 청구서 내역 Link field and then uncheck “Show Inverse Relationship”.

Then re-enable the “Show Inverse Relationship” option and the field will look proper again like a Table as it should for the inverse of a Join relationship.

As for the Pick List and the table field you were typing into, it looked like everything you typed was set the same as when you exited the fields. The same for the Pick List. That all looked ok to me.

[Yoo Byeng Han]

Thank you for answer

The pick list now has no problems when typing Hangul.

However, in the portal, Hangul input is still required to double click on the fielder.
If you enter an alphabet or number, it is not the same as selecting a field and typing it straight away.

Watch the video again

https://www.dropbox.com/s/xp2vscuonpfu8de/potal%20problem.mp4?dl=0

[Author]

Posts