Yvon Steinthal Active Member Licensed User Longtime User Feb 29, 2016 #1 Hi, I am currently trying to add a custom keyboard in B4i for an iOS app. So far i've figured that the keyboard is called upon the KeyboardStateChanged Event. My question is simple, how can i forbid the keyboard to pop up, and instead show my custom keyboard. (a custom panel with custom buttons basically...) Any clues or advice would be appreciated.
Hi, I am currently trying to add a custom keyboard in B4i for an iOS app. So far i've figured that the keyboard is called upon the KeyboardStateChanged Event. My question is simple, how can i forbid the keyboard to pop up, and instead show my custom keyboard. (a custom panel with custom buttons basically...) Any clues or advice would be appreciated.
tufanv Expert Licensed User Longtime User Aug 29, 2018 #21 jai said: Can you please share how this problem was resolved. I am facing the same issue. Click to expand... Can't remember what i did but my current working code use this : Code: Copy Dim no As NativeObject=txthesap no.setField("inputView", panelmakine2) panelmakine2 loads a layout file that has the numbers of the keypad etc.. Upvote 0
jai said: Can you please share how this problem was resolved. I am facing the same issue. Click to expand... Can't remember what i did but my current working code use this : Code: Copy Dim no As NativeObject=txthesap no.setField("inputView", panelmakine2) panelmakine2 loads a layout file that has the numbers of the keypad etc..
J jai Active Member Licensed User Longtime User Aug 29, 2018 #22 tufanv said: Can't remember what i did but my current working code use this : Code: Copy Dim no As NativeObject=txthesap no.setField("inputView", panelmakine2) panelmakine2 loads a layout file that has the numbers of the keypad etc.. Click to expand... I keep on getting (when tap on txthesap)- child view controller:<UICompatibilityInputViewController: 0x143e3a720> should have parent view controllerage (vc): Page but requested parent is:<UIInputWindowController: 0x14408da00> Just to confirm, txthesap is a TextField panelmakine2 is a panel Both are initialized in the layout file in Main. Above code is placed immediately after LoadLayout in Application_Start, panelmakine2 has views in it. How does panelmakine2 load layout files? This is where my problem may be. Can you please elaborate a bit more with an example. Upvote 0
tufanv said: Can't remember what i did but my current working code use this : Code: Copy Dim no As NativeObject=txthesap no.setField("inputView", panelmakine2) panelmakine2 loads a layout file that has the numbers of the keypad etc.. Click to expand... I keep on getting (when tap on txthesap)- child view controller:<UICompatibilityInputViewController: 0x143e3a720> should have parent view controllerage (vc): Page but requested parent is:<UIInputWindowController: 0x14408da00> Just to confirm, txthesap is a TextField panelmakine2 is a panel Both are initialized in the layout file in Main. Above code is placed immediately after LoadLayout in Application_Start, panelmakine2 has views in it. How does panelmakine2 load layout files? This is where my problem may be. Can you please elaborate a bit more with an example.
J jai Active Member Licensed User Longtime User Aug 29, 2018 #23 tufanv said: Can't remember what i did but my current working code use this : Code: Copy Dim no As NativeObject=txthesap no.setField("inputView", panelmakine2) panelmakine2 loads a layout file that has the numbers of the keypad etc.. Click to expand... Thanks tufanv! I figured it out. Upvote 0
tufanv said: Can't remember what i did but my current working code use this : Code: Copy Dim no As NativeObject=txthesap no.setField("inputView", panelmakine2) panelmakine2 loads a layout file that has the numbers of the keypad etc.. Click to expand... Thanks tufanv! I figured it out.
tufanv Expert Licensed User Longtime User Aug 30, 2018 #24 jai said: Thanks tufanv! I figured it out. Click to expand... Good ! What was the problem ? Upvote 0
J jai Active Member Licensed User Longtime User Sep 25, 2018 #25 tufanv said: Good ! What was the problem ? Click to expand... The Dim and no.SetField statements for all associated views had to be listed immediately after loading the layout for it to work. I had some other statements in between and moving them to a later point made it work as needed. Upvote 0
tufanv said: Good ! What was the problem ? Click to expand... The Dim and no.SetField statements for all associated views had to be listed immediately after loading the layout for it to work. I had some other statements in between and moving them to a later point made it work as needed.
