// Copyright (C) 2024 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only

// **********************************************************************
// NOTE: the sections are not ordered by their logical order to avoid
// reshuffling the file each time the index order changes (i.e., often).
// Run the fixnavi.pl script to adjust the links to the index order.
// **********************************************************************

/*!
    \page creator-known-issues.html
    \previouspage creator-reference.html

    \ingroup creator-reference

    \title Known issues

    \summary {Known issues in \QC version \qtcversion.}

    The \QC development team is aware of the issues described here, and
    therefore, you do not need to report them in the \l{Qt Project Bug Tracker}.
    However, if you run into these issues,
    feel free to check the links to the applicable bug ticket
    and add your vote or any additional information you might have
    about your development environment.

    For a list of fixed issues and added features, go to \uicontrol Help >
    \uicontrol {Change Log}.

    \section1 General issues

    \list

        \li  If you change the Input Languages in Windows, \QC might not
            respond for 30 seconds. This is a known issue in the Advanced Text
            Service of Microsoft Windows.

        \li  \QC uses SQLite for storing some of its settings. SQLite is
            known to have problems with certain NFS servers (most notably the
            nfs-user-server 2.2beta), since they can lock up the application
            when it tries to lock the database. If your home directory is on an
            NFS share and you encounter this issue, one option would be to
            switch to the nfs-kernel-server, or create a symlink so that the
            settings are stored locally.

        \li  The Okteta KDE custom widget plugin might be installed as part of
            some Linux distributions. It can cause \QD to crash. For
            more information, see:

            \list

                \li  \l{Ubuntu bug 662005}

                \li  \l{QTBUG-12025}

           \endlist

            To resolve the issue, enter the following command to remove the
            package:
            \code
            sudo apt-get remove okteta
            \endcode
            Or delete the following file:
            \c /usr/lib/kde4/plugins/designer/oktetadesignerplugin.so.

    \endlist

    \section1 Editing issues

    \list

        \li Code completion does not support typedefs for nested classes.

        \li When developing on Linux, the \key {Ctrl+Shift+U} keyboard shortcut
            might not work because it conflicts with a shortcut of the
            Intelligent Input Bus (ibus). You can change either the shortcut in
            \QC or the conflicting shortcut in ibus.

            To set another \l {Keyboard shortcuts}{keyboard shortcut}
            in \QC, select \preferences >
            \uicontrol Environment > \uicontrol Keyboard.

            To change the ibus shortcut, enter the following command on the
            command line to start ibus setup:
            \code [shell]
            ibus-setup
            \endcode

            Then, change the unicode code point shortcut in the \uicontrol Emoji
            tab to something else than \key {<Control><Shift>u}.
    \endlist

    \section1 Projects issues

    \list

        \li  Paths or file names that have spaces or special characters
            (such as colons, dollar signs, and hash marks) may cause problems.
            This is because some of the tools \QC uses in the background have
            restrictions on the characters allowed in file and directory names.
            To be on the safe side, we recommend creating projects and project
            items with names consisting of plain characters, numbers,
            underscores, and hyphens.

        \li  If error messages displayed in \l {Compile Output} have
            paths where slashes are missing (for example, C:QtSDK),
            check your PATH variable. For more information, see
            \l{Troubleshoot MinGW compilation errors}.

    \endlist

    \section1 Debugging issues

    \list

        \li  GDB on Windows may not work if the 'Embassy \reg Security Center'
            software by 'Wave \reg Systems' is installed and active (causing
            crashes in \c{vxvault.dll}).

        \li  GDB may take long to load debugging symbols, especially from large
            libraries.

        \li  Setting breakpoints in code that is compiled into the binary more
            than once does not work.

        \li  Setting breakpoints in files that do not have unique absolute
            paths may fail. For example, remounting parts of a file system
            using the \c {--bind mount} option.

        \li  Setting breakpoints in files will fail when using LLDB if the file path
            has symbolic links.

    \endlist
*/
