Thanks for the replies. Yes, it seems QT_TR_NOOP and QT_TRANSLATE_NOOP are what I was looking for in the absence of QCoreApplication, and Q_DECLARE_TR_FUNCTIONS in the case where QCoreApplication is available. Whether we have QCoreApplication available or not is still an open question, but something for a different discussion thread I think.
The MATLAB installation does have the header files in it. I realized the INCLUDEPATH in the .pro file put in the path for the location of these header files and tried going to it in my terminal, only to realize a small typo needing to change /Applications/MATLAB_R2018b.app/extern/include/ to /Applications/MATLAB_R2018a.app/extern/include/. Changing that got rid of those errors. Thanks!
Unfortunately, NodeMetaInfo does not support enumerating methods. The code model does support this, though.
You could add the functionality to NodeMetaInfo by extending the MemberProcessor and implementing processSlot() similar to how processSignal() is implemented.
How to handle function parameters you can lookup in qmljseditor.cpp for the implementation of CodeModelInspector.
Thanks for answering.
I do have both the NDK and SDK (and the path are set in QtCreator) so it should not be a problem, right ? Or do I need to add the compiler manually ? How can I find it ?
I don't know Android good enough to help you here.
I understand that UWP compilers only comes with MSVC. What about windows 64bit ?
Same, thanks to licensing :( You also need the Debugging Tools for Windows to have a debugger.
I installed MinGW 64bits compiler during the installation procedure, but they were no prebuilt component for MinGW 64bits, only for Win 64 MSVC. I guess I have to set it up manually ?
Qt 5.12 will be MinGW64, IIRC. For 5.11, install the correct 32 bit MinGW version, or compile Qt from source with MinGW64 if you need it.
@qtcat Did you build your app?
ui_mainwindow.h is a file which is generated during build. If it is not yet there (because you did not yet build), QtCreator will show this errors/warnings because it does not know what Ui::MainWindow, which comes from that generated file, is.
I'm using QT Creator 4.5.2 now. And this hasn't become an option yet. Switching to design mode is counter-intuitive to me - I'm a programmer and more comfortable around codes than fancy ui. Looks like QT is really pushing hard their design mode to their users. Ended up grabbing the source and commented out the auto-switching to design mode. For anyone looking, it is in src/plugins/coreplugin/editormanager/editormanager.cpp. Interestingly, they have all sorts of flags on whether to switch to modes automatically each time a file loads so it should actually be quite configurable with little effort. Being a lazy man though, I just commented out one branch of an if-clause between line 1264 - 1278, recompile and voila! I don't need to wait for qtcreator to load the design mode screen now :D
I did this in the v4.5.2 source. If anyone knows any updates since this version, like a checkbox to handle this behavior, please tell me :D
@M.O.H If you want some improvements in QtCreator (not CtCreator) then you should go to Qt bug tracker and file a request there. This is a user forum, it does not make sense to request changes in QtCreator here.