OverviewFelgo 2 Support (Qt 5) › Getting sizes of nativeUtils dialogs and system keyboards

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #20523

    Felgo User


    A few related questions (I’ve looked through your documentation but can’t find anything, if I’ve missed something, please let me know):

    1. I currently have a working timePicker, displayed in a standard Dialog {}, but I want it to have the same look as nativeUtils.displayDatePicker(). Where can I find the information on size, corner radius, etc. of the native date picker? Or is there a way to simply open the native date picker dialog and replace everything inside with my time picker? (Quick follow up: Why is there no native time picker, why only date picker?)
    2. Is there a way to get the size of the keyboard that the system opens when user input is required? I need to be able to add space at the bottom of the page equal to the keyboard size so the user can scroll up and see the “Submit” button even when the keyboard is still showing.
    3. When requiring user input to be numbers only, the number keypad the system displays doesn’t have a “Done” button like the full keyboard does. I know the users can swipe down to close it but I would like a more obvious way for them to close the keypad. Is there a function that will do this (so I can add a button somewhere)? Or is there a better way to handle this?

    Thank you very much for your time and help.



    Felgo Team


    • It is not possible to modify native dialogs. The look and behavior is set by the native platform. We did not yet add native time pickers to the available NativeUtils features as it was requested only rarely up till now and QML-based dialogs are a good alternative and also customizable.
    • You can have a look at the App::keyboardVisible and App::keyboardHeight properties for improved keyboard handling in your pages.
    • The keyboard behavior and features depend on the native platform. You cannot modify it from your app. However, you can close the keyboard by moving the Focus / Cursor away from the input field programatically. You can do so by calling forceActiveFocus() on another QML item on your page.


Viewing 2 posts - 1 through 2 (of 2 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Voted #1 for:

  • Easiest to learn
  • Most time saving
  • Best support

Develop Cross-Platform Apps and Games 50% Faster!

  • Voted the best supported, most time-saving and easiest to learn cross-platform development tool
  • Based on the Qt framework, with native performance and appearance on all platforms including iOS and Android
  • Offers a variety of plugins to monetize, analyze and engage users
create apps
create games
cross platform
native performance
3rd party services
game network
level editor
easiest to learn
biggest time saving
best support