Discussion Board

Results 1 to 4 of 4
  1. #1
    Registered User
    Join Date
    Feb 2010

    Disabling split view input for text editors


    Could someone tell me how to disable split view input for text editors? In my application, even newly created ones, the input fields that are in lower part of the screen get covered up by the keyboard. They don't move up above the keyboard as shown here.

    Is there a way to force full screen input in application or to fix moving of text input fields so they're not covered up by keyboard?

    I tried

        // Enable partial screen text input keyboard for the application
        QCoreApplication::setAttribute(Qt::AA_S60DisablePartialScreenInputMode, true);
    and it has no effect. Even setting it to false has no effect.

  2. #2
    Nokia Developer Moderator
    Join Date
    Mar 2003

    Re: Disabling split view input for text editors

    According to docs,: http://doc.qt.nokia.com/4.7-snapshot/qt.html the split view should be off by default. and only on if you specify so..

  3. #3
    Registered User
    Join Date
    Feb 2010

    Re: Disabling split view input for text editors

    True, which is why this is so frustrating. So, if you could think of anything to try to fix this I would be grateful. I'm on a deadline and this was the least expected problem.

    Please look at the following sample project created just for this post. It's an automatically generated Qt Quick application with Qt Quick Components for Symbian. I just removed the hello world and put in a TextField. Here's what happens on Nokia C7:

    At application start up:

    If you tap the TextField:

    According to documentation here you enable this by changing this attribute:

    QCoreApplication::setAttribute(Qt::AA_S60DisablePartialScreenInputMode, false);
    I didn't touch that attribute. And even if I set the attribute to true by adding the following line to main.cpp:
    QCoreApplication::setAttribute(Qt::AA_S60DisablePartialScreenInputMode, true);
    The application behaves the same.

    I'm testing this on Nokia C7

    Release: Symbian Belle
    Sw. version: 111.030.0609
    Sw. ver. date: 2011-11-26
    Custom ver.: 111.030.0609.00.1
    Language set: 111.030.0609.07.01
    Product code 095D8K6
    Model: C7-00
    Type: RM-675

    Building with Qt 4.7.4.for Symbian Belle.

    Here's main.cpp

    #include <QtGui/QApplication>
    #include "qmlapplicationviewer.h"
    Q_DECL_EXPORT int main(int argc, char *argv[])
        QScopedPointer<QApplication> app(createApplication(argc, argv));
        QmlApplicationViewer viewer;
        return app->exec();
    Here's main.qml

    import QtQuick 1.1
    import com.nokia.symbian 1.1
    PageStackWindow {
        id: window
        initialPage: MainPage {tools: toolBarLayout}
        showStatusBar: true
        showToolBar: true
        ToolBarLayout {
            id: toolBarLayout
            ToolButton {
                flat: true
                iconSource: "toolbar-back"
                onClicked: window.pageStack.depth <= 1 ? Qt.quit() : window.pageStack.pop()

    import QtQuick 1.1
    import com.nokia.symbian 1.1
    Page {
        id: mainPage
        TextField {
            anchors.horizontalCenter: mainPage.horizontalCenter
            anchors.bottom: mainPage.bottom
            placeholderText: "Enter Text Here"
    And the .pro file

    # Add more folders to ship with the application, here
    folder_01.source = qml/TestingInputKeyboard
    folder_01.target = qml
    # Additional import path used to resolve QML modules in Creator's code model
    symbian:TARGET.UID3 = 0xE73EAADB
    # Smart Installer package's UID
    # This UID is from the protected range and therefore the package will
    # fail to install if self-signed. By default qmake uses the unprotected
    # range value if unprotected UID is defined for the application and
    # 0x2002CCCF value if protected UID is given to the application
    #symbian:DEPLOYMENT.installer_header = 0x2002CCCF
    # Allow network access on Symbian
    symbian:TARGET.CAPABILITY += NetworkServices
    # If your application uses the Qt Mobility libraries, uncomment the following
    # lines and add the respective components to the MOBILITY variable.
    # CONFIG += mobility
    # MOBILITY +=
    # Speed up launching on MeeGo/Harmattan when using applauncherd daemon
    # CONFIG += qdeclarative-boostable
    # Add dependency to Symbian components
    CONFIG += qt-components
    # The .cpp file which was generated for your project. Feel free to hack it.
    SOURCES += main.cpp
    # Please do not modify the following two lines. Required for deployment.

  4. #4
    Registered User
    Join Date
    Feb 2010

    Re: Disabling split view input for text editors

    Well, found the error.

    While the Qt::AA_S60DisablePartialScreenInputMode has no effect. There is an attribute called platformSoftwareInputPanelEnabled : bool in PageStackWindow that enables moving the component.

Similar Threads

  1. Disabling predictive text input flash lite actionscript 2 - how do you do it?
    By kyazdani in forum [Archived] Flash Lite on Nokia Devices
    Replies: 3
    Last Post: 2011-11-05, 22:32
  2. Creating a view with 2 text editors
    By mikah in forum Symbian User Interface
    Replies: 3
    Last Post: 2009-02-25, 13:18
  3. Replies: 4
    Last Post: 2008-08-25, 11:06
  4. Replies: 1
    Last Post: 2003-03-26, 10:04

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts