CoronaEnterprise.2013.1251 - iOS 7 Korean native.newTextField input Problem.

zetaloki4 · November 6, 2013, 5:47am

Hi, Brent.

Thank you very much for your rapid reply

zetaloki4 · November 7, 2013, 10:30am

Hi, Brent.

We tested more and tried to find solution. But, unfortunately we cannot found how to solve this issue.

(Including 2013.1256 enterprise and simulator iOS build)

Here’s my code actually using.

There’s no logic clipping, changing of string.

--... --------------------------- -- Read filter words from file local filterChat local path = system.pathForFile( 'etc/filterChat.txt', system.ResourceDirectory ) local fileObject, errStr = io.open( path, 'r' ) path = nil if fileObject == nil then &nbsp;&nbsp;&nbsp;&nbsp;-- no file no filtering &nbsp;&nbsp;&nbsp;&nbsp;filterChat = {} else &nbsp;&nbsp;&nbsp;&nbsp;local filterChatStr = fileObject:read( '\*a' ) &nbsp;&nbsp;&nbsp;&nbsp;-- split into array &nbsp;&nbsp;&nbsp;&nbsp;filterChat = lib.split( filterChatStr, '\n' ) &nbsp;&nbsp;&nbsp;&nbsp;filterChatStr = nil &nbsp;&nbsp;&nbsp;&nbsp;io.close( fileObject ) end -- 5783 words print('filterChat count: '..#filterChat) ------------------------------------- -- Validate input string local function validateChat( str ) &nbsp;&nbsp;&nbsp;&nbsp;if str == nil or str == '' then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return false &nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;if string.find(str, '[^%a%d%p%sㄱ-ㅎ가-힣]') ~= nil then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- cannot input character except english, number, korean &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lib:confirmCheck{ msg='영문, 숫자, 한글 이 외의 문자는 입력할 수 없어요', type='normal' } &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return false &nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;-- 글자 수 &nbsp;&nbsp;&nbsp;&nbsp;local koreanByteSize = 0 &nbsp;&nbsp;&nbsp;&nbsp;for chr in string.gfind(str, '[ㄱ-ㅎ가-힣]') do &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;koreanByteSize = koreanByteSize + 1 &nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;local normalChar = 0 &nbsp;&nbsp;&nbsp;&nbsp;for word in string.gfind(str, '[%a%d%p%s]') do &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;normalChar = normalChar + 1 &nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;local byteCount = normalChar + (koreanByteSize/3)\*2 &nbsp;&nbsp;&nbsp;&nbsp;if byteCount \> 80 then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lib:confirmCheck{ msg='입력 글자는 한글40자, 영문80자를 넘을 수 없어요', type='normal' } &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return false &nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;-- 금칙어 체크 &nbsp;&nbsp;&nbsp;&nbsp;for i = #filterChat, 1, -1 do &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- remove ? character from filter list &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if str:find( filterChat[i]:gsub('?', '') ) ~= nil then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- there's unallowed word &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lib:confirmCheck{ msg='금칙어가 포함되어 있습니다.', type='normal' } &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return false &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;return true end --------------------------------------- -- input field self.ui.textField = native.newTextField( 60, 590-26, 650, 53, function(e) &nbsp;&nbsp;&nbsp;&nbsp;if e.phase == "began" then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- user begins editing textField &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if system.getInfo('platformName') == 'iPhone OS' then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e.target.y = 270 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;elseif e.phase == "ended" then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- textField/Box loses focus &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- Hide keyboard &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;native.setKeyboardFocus( nil ) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if system.getInfo('platformName') == 'iPhone OS' then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e.target.y = 590 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;elseif e.phase == "submitted" then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- Hide keyboard &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;native.setKeyboardFocus( nil ) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if system.getInfo('platformName') == 'iPhone OS' then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e.target.y = 590 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;local inputText = e.target.text &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- Validate &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if not validateChat( inputText ) then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return false &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- OK!! SEND!!! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;M:send{ type='chat', msg=inputText } &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inputText = nil &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e.target.text = '' &nbsp;&nbsp;&nbsp;&nbsp;elseif e.phase == "editing" then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- NONE &nbsp;&nbsp;&nbsp;&nbsp;end end) self.ui.textField.align = 'left' self.ui.textField.size = 10 self.ui.textField.font = native.newFont( DEF\_FONT, 10 ) self.ui.textField.y = 590 --...

bjsorrentino · November 7, 2013, 10:51pm

Hi @zetaloki4,

Do you have a public build or recent daily (non-Enterprise), like #1202 or #1256? If so, could you test out the Corona sample app for text fields? It’s located here:

CoronaSDK > SampleCode > Interface > NativeKeyboard

In my on-device tests using #1256 (again, non-Enterprise), I was able to get Korean characters input into a text field (using the iPhone5’s Korean keyboard), then when I re-opened the text box, the same characters were there… no clipping had occurred. I tested this with several variances of Korean characters, including ending the sentences with a period or a regular character.

So, if you can test this, it may reveal if the issue is related to Enterprise, or something else.

Thanks,

Brent

zetaloki4 · November 8, 2013, 5:42am

Hi, Brent.

I checked all.

The problem is textField object’s string value (textField.text). Not displaying.

You can reprise this with “NativeKeyboard” sample project replacing fieldHandler function with code bellow.

You should type the Korean character manually. Copy and paste does not occurs problem.

(Attached result screenshot.)

local function fieldHandler( textField ) &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;local lineCount = 0 &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;return function( event ) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if ( "began" == event.phase ) then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;elseif ( "ended" == event.phase ) then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;elseif ( "editing" == event.phase ) then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;elseif ( "submitted" == event.phase ) then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- If you input korean text like 안녕 or 안녕하세요, displaying of text field is ok. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- But, textField().text value would be 안녀ㅇ, 안녕하셍ㅛ that is unexpected result. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;print( 'Final text value: '..textField().text ) --\> Unexpected result... &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;----------------- DEBUG: DRAW TEXT ON SCREEN ---------------- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;local temp = display.newText( textField().text, 0, 270 + lineCount \* 16, nil, 16 ) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;temp:setTextColor(0,255,0) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lineCount = lineCount + 1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;------------------------------------------------------ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-- Hide keyboard &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;native.setKeyboardFocus( nil ) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;end &nbsp;&nbsp;&nbsp;&nbsp;end end &nbsp;

XCODE (iPhone device connected) organizer console outputs like this…

Nov 8 14:47:50 im-utaeg-i NativeKeyboard[11771] <Warning>: Final text value: 안녕하셍ㅛ

Nov 8 14:47:54 im-utaeg-i NativeKeyboard[11771] <Warning>: Final text value: 안녀ㅇ

Best regards.

ingemar · November 8, 2013, 8:45am

OSX Mavericks 10.9

Xcode 5.0.2 (5A3005)

Corona SDK: 2013.1257 Standard version (not Enterprise)

Sample Project: NativeKeyboard (without modifications necessary)

I can confirm this behavior on iOS6 and iOS7. When entering the word ‘안녕’, it appears correctly on the display, but outputs the following to the console log on the device:

NativeKeyboard[26488] <Warning>: 안녀ㅇ

However as the OP has observed, if you enter a character after the last ‘ㅇ’ (like a space or a number), the output in the log will be correct (NativeKeyboard[26488] <Warning>: 안녕).

NOTE:

Entering Korean text when running the sample app in the Corona Simulator will crash the simulator.

zetaloki4 · November 18, 2013, 12:00pm

Hi, Brent.

Would you mind tell me about progression for iOS textfield? or any plan to fix this.

Thank you.

bjsorrentino · November 18, 2013, 7:25pm

Hi @zetaloki4,

We’re still checking into it; thanks for your patience and your detailed reports (and Ingemar too).

Best regards,

Brent

bjsorrentino · November 20, 2013, 12:21am

Hi @zetaloki4,

We have implemented a fix for this, and it should be available to you within the next couple days via a daily build.

Sincerely,

Brent

zetaloki4 · November 20, 2013, 6:15am

That sounds great!