For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 6 replies, 3 voices, and was last updated 13 years, 3 months ago by
.
-
Posts
-
1) Induce the touch keypad used on the iPad to include the ‘Done’ button on its ?menu bar? – the grey bar that appears immediately above the keypad when it is visible.
2) Make the m1 multipage tabbar use custom transitions — I can see how to do this by hacking either the auto generated .html file or the corresponding .js file, but before the App is entirely finished this is going to be a ‘every single test/compilation task’ and creates a long-term maintenance nightmare for the future.
Hi Stu,
>1) Induce the touch keypad used on the iPad to include the ‘Done’ button on its ?menu bar? – the grey bar that appears immediately above the keypad when it is visible.
The Done button appears on a the keyboard dialog when the input widget is on a screen with the Form property enabled.>2) Make the m1 multipage tabbar use custom transitions — I can see how to do this by hacking either the auto generated .html file or the corresponding .js file, but before the App is entirely finished this is going to be a ‘every single test/compilation task’ and creates a long-term maintenance nightmare for the future.
It is possible to specify a transition between the page changes of a multipage widget using the OnClick GotoPage action. But this action is not available from the TabBar buttons.@support-octavio wrote:
>1) Induce the touch keypad used on the iPad to include the ‘Done’ button on its ?menu bar? – the grey bar that appears immediately above the keypad when it is visible.
The Done button appears on a the keyboard dialog when the input widget is on a screen with the Form property enabled.Sadly, not the case with either WebApp or iOS.
Any other ideas…Exactly, but it doesn’t happen on my iPad. The first .mobi has four text boxes, the rest of the screens only have read only text boxes. The first .mobi was as you show form checked with no action (I tried it with actions as well) and the only things on the bar are previous, next and autofill. Both as a WebApp and an iOS app I failed to get the done button.
On a related note, I got a strange artefact. In my original design three of the text entries were above the middle of the screen, but the fourth fell below the centre line in landscape. When, one touched the lowest text box, as expected the keypad slid up and the screen moved up and compressed, but as soon as you start typing the background slides up another couple of centimetres exposing a white substrate which ‘conceals’ the text box and spoils the cosmetics of the app. Moving all four widgets above the centre line stops this problem.
I’m driving an iPad 2 running iOS 6.1.3
… Added in edit …
The done button does appear on my iphone4 … But the app is not designed for that formatHi Stu,
I’m not sure what else can be done. There is no api for tweaking the form input dialog. If you post a small example project we can test drive it and see if there is something else that can be done.
Thanks for trying.
My basic problem is that I would like these inputs to be provided prior to entry to the app proper. The mechanics of the keyboard hide any tab bar and a nav bar slides off the top of the screen. Result, the user has no obvious way forward … A done button would greatly improve the situation. Of course, there is always the dismiss keyboard key at the bottom right, but most users are in my limited experience unfamiliar with its use.
