4 ms·

I use Visual Studio 2017 to develop a Qt application on Windows. I use Qt Creator (QtC) for same app on macOS. I love Qt, am delighted to have converted from Wi

I use Visual Studio 2017 to develop a Qt application on Windows. I use Qt Creator (QtC) for same app on macOS. I love Qt, am delighted to have converted from Win32. Sorry but VS still feels as solid as a tank, Qt Creator is less responsive to my needs. - 'asserts' in QtC bring the debug session to a grinding halt. I can't step over like I can in VS. - Where can I define macros in QtC? - In debug mode, QtC is unable to display certain types of variables, way too often. - I have fiddled for days with the .PRO file, read all the StackOveflow posts, and I still can't suppress reams of pedantic warnings. - QtC just gives the impression of a rudimentary attempt at VS, like things are about to fall apart at any moment. To a programmer accustomed to VS, there always seems to be something missing, and I don't mean just different keyboard shortcuts. QtC has a long way to go. Still, it's better than a text editor and the command line.

jcelerier 7y ago
Fun, I have exactly the opposite experience re. VS and Qt Creator - VS sometimes takes, like 15 minutes to start a debug session on a large project while QtC can get to work in the same time that it would take gdb to start. And that's without counting the clang-based code model, all the niceties under the locator (ctrl-k), etc etc > Where can I define macros in QtC? the IDE is imho not the place to do that. Just use CMake and target_compile_definitions(my_target PRIVATE MY_MACRO=123) > - In debug mode, QtC is unable to display certain types of variables, way too often. very strange, but then I mostly use it on Linux with gdb / lldb, maybe the cdb integration is less good. > - I have fiddled for days with the .PRO file, read all the StackOveflow posts, and I still can't suppress reams of pedantic warnings If CONFIG += warn_off in your .pro (switch to cmake !!!) does not work please file bugs !
- TravHatesMe 7y ago
  Not sure if this applies to Qt, but VS2019/netcore has made tremendous strides with its tiered compilation.
- GnarfGnarf 7y ago
  Sorry, I meant keyboard shortcut macros (Ctrl M, R in VS 2017).
  - jcelerier 7y ago
    hmm.. this ? https://doc.qt.io/qtcreator/creator-macros.html https://doc.qt.io/qtcreator/creator-macros.html

jcelerier 7y ago

Fun, I have exactly the opposite experience re. VS and Qt Creator - VS sometimes takes, like 15 minutes to start a debug session on a large project while QtC can get to work in the same time that it would take gdb to start. And that's without counting the clang-based code model, all the niceties under the locator (ctrl-k), etc etc > Where can I define macros in QtC? the IDE is imho not the place to do that. Just use CMake and target_compile_definitions(my_target PRIVATE MY_MACRO=123) > - In debug mode, QtC is unable to display certain types of variables, way too often. very strange, but then I mostly use it on Linux with gdb / lldb, maybe the cdb integration is less good. > - I have fiddled for days with the .PRO file, read all the StackOveflow posts, and I still can't suppress reams of pedantic warnings If CONFIG += warn_off in your .pro (switch to cmake !!!) does not work please file bugs !

TravHatesMe 7y ago
Not sure if this applies to Qt, but VS2019/netcore has made tremendous strides with its tiered compilation.
GnarfGnarf 7y ago
Sorry, I meant keyboard shortcut macros (Ctrl M, R in VS 2017).
- jcelerier 7y ago
  hmm.. this ? https://doc.qt.io/qtcreator/creator-macros.html https://doc.qt.io/qtcreator/creator-macros.html