Skip to content

Qt Creator and other tools

Have a question about Qt Creator, our cross-platform IDE, or any of the other tools? Ask here!
7.6k Topics 35.3k Posts
  • QT creator and MinGW project in C doesn't recognize ncurses.h

    Unsolved
    9
    0 Votes
    9 Posts
    1k Views
    aha_1980A
    @mzimmers I notice the OP is using backslashes in his path. As I recall, this causes problems in a project file. Correct. Using forward slashes is the way to go. The other thing is that the -L/-l convention comes from Linux; does this actually work with Windows libraries? I seem to recall trying to use that once, and ran into issues I can't remember anymore. Using -L and -l is cross-platform and should be used on Windows with MSVC and MinGW also. Qt Creator recognizes this syntax and extends the library search paths when running the app. If you have problems here, then you probably messed up the syntax - which I had in former times also ;) Regards
  • Remote Debugging

    Solved
    10
    0 Votes
    10 Posts
    2k Views
    ODБOïO
    Worked with gdbserver verson 7.9.1
  • Hide *.pri include in Project Tree

    9
    0 Votes
    9 Posts
    6k Views
    X
    Is there still no elegant solution to this? Can not get "load" to work, and another post suggests it might be broken.
  • Adding kits and Qt mkspec

    Moved Solved
    4
    0 Votes
    4 Posts
    328 Views
    R
    Yes it would seem it's looking for the full location. Seems like you should be able to browse for the directory here, perhaps this is a bug? In any case, I will mark this as solved.
  • changing editor line color - grayed out

    Moved Unsolved
    2
    0 Votes
    2 Posts
    234 Views
    Christian EhrlicherC
    You can't change the default scheme, you have to create a new one.
  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    5 Views
    No one has replied
  • Is there a shortcut for "select next occurrance"?

    Unsolved keybindings qt creator
    20
    0 Votes
    20 Posts
    6k Views
    B
    @aha_1980 Yes, I've just read the report and yes, that's exactly want I wanted to do! I'll definitely vote there, tank you! :)
  • Need to specify a INCLUDE and LIB environment manually -_-!

    Unsolved
    7
    0 Votes
    7 Posts
    1k Views
    Q
    @jsulm Still unresolved, thanks any way.
  • Qt Designer: copy and paste? Drag and Drop (with option key for "duplicate")?

    Solved
    13
    0 Votes
    13 Posts
    10k Views
    J
    Hey, I hope this is not awfully late. I've had the same problem with copy and pasting and found the easiest way to evade it is to use CTRL + (drag widget) instead.
  • How to disable "Qt VS Tools: QML debug" message

    Unsolved
    7
    3 Votes
    7 Posts
    2k Views
    J
    @jsulm Sorry, added comment to https://bugreports.qt.io/browse/QTVSADDINBUG-837
  • Resource Icons in Qt Linguist

    Unsolved
    2
    0 Votes
    2 Posts
    221 Views
    Christian EhrlicherC
    I don't think this will work - the preview is just a simple helper ui to show you where the text is in the dialog.
  • How to customize Python editor warnings?

    Unsolved
    1
    0 Votes
    1 Posts
    245 Views
    No one has replied
  • How to attach multiple files in the files bar

    Unsolved
    5
    0 Votes
    5 Posts
    560 Views
    Christian EhrlicherC
    @Arus23 said in How to attach multiple files in the files bar: on someone's else computer and he had it like that in Qt Creator. For sure not. Use the 'open files' window or Strg+Tab
  • Cannot build with cmake, qtcreator and MSVC 2019

    Solved
    10
    0 Votes
    10 Posts
    9k Views
    K
    Okay, found it. The error is with the "<unsupported>" keyword that should not be here. In tools > options > Kits > Desktop Qt XXX > CMake Generator > Platform & Toolset, the string "<unsupported>" has appeared. These fields should be cleared. These fields content has been automatically copied to : project tab > CMake > Initial CMake parameters ; fields -A<unsupported> and -T<unsupported> that should be removed. Once the fields are cleared, I have to do : Compile > Clear CMake configuration Compile > Execute CMake Build All Projects If a build error happens (non existing project file or target) : project tab > build steps > build > targets > choose the right target Build All Projects Then it works, with encoding errors but it builds normally! (enjoy) I opened new tickets in the Qt bug tracker : Cannot build a new project with CMake and MSVC without modifying the target Value <unsupported> should not appear in CMake platform & Toolset Bad encoding in CMake compilation output and problems panel on Windows
  • Qt Creator space between function name and opening parameter bracket

    Solved
    5
    0 Votes
    5 Posts
    953 Views
    P
    After a bit over a year, I finally found the reason. :-) Tools -> Options -> Text Editor -> Completion The checkbox to tick is "Insert space after function name".
  • Console settings

    Locked Unsolved
    2
    0 Votes
    2 Posts
    269 Views
    SGaistS
    Hi and welcome to devnet, Please do not post the same question in multiple sub forum. One is enough. Closing this one. Duplicate
  • QtCreator CDB crashing except if I "clear system environment"

    Solved
    7
    0 Votes
    7 Posts
    599 Views
    K
    CMake, QMake, Python: lots of things are shipped with QtCreator. If I install QtCreator on a clean windows, everything will work fine. However, I still don't have CMake working... If you have a lead it would be great : https://forum.qt.io/topic/120275/cannot-build-with-cmake-qtcreator-and-msvc-2019
  • way to get cell's size of QGridLayout

    Unsolved
    8
    0 Votes
    8 Posts
    1k Views
    Christian EhrlicherC
    Maybe take a look into the designer sources will help you.
  • Autocompletion Does Not Work Reliably With g++ 9 and 10

    Moved Unsolved autocompletion gcc
    3
    0 Votes
    3 Posts
    690 Views
    J
    @JonB If you mean ClangCodeModel plugin, no. I deselected that.
  • Qt VS Tools environment corrupt? moc trying to compile .ui files

    Solved
    5
    0 Votes
    5 Posts
    655 Views
    K
    Updating to rev.7 fixed it for me also. Previous revision was broken.