Qt Creator and other tools

@aha_1980 Thanks!

What do you mean "I installed it with QtSdkRepoChooser"

@aha_1980 said in QtCreator updated and float type is not highlighted in C any more: I said that "bool, true and false" are not highlighted anymore. And by disabling "false", "float" was disabled too, sorry. The fix is under review: https://codereview.qt-project.org/205025 So I guess this can be closed as solved.

I've partialy analysed AutoTest code. For QTest it checks if given source file (after macro preprocesing) has QTest include and QTest::exec() somewhere in code. In my case it lead to usage of TestRunner modified to store function object #define DECLARE_TEST_RUNNER(className) \ namespace { \ int executeTestClass(int argc, char* argv[]) \ { \ className test; \ return QTest::qExec(&test, argc, argv); \ }; \ static char test_##className = \ TestRunner::Instance().RegisterTestClassRunner(executeTestClass); \ } Macro is placed at begining of each CPP file with test details (to decouple as much as possible) However Autotest still acts strangely. Sometimes it discover tests, sometimes not. I believe that it may search in source context of currently selected run target. PS: When I expanded one of DECLARE_TEST_RUNNER macro - AutoTest start displaying green arrows. Not before. Building main exe or ut.exe isn't helping. Calling 'Refresh test' from Tools->Tests also doesn't help. I still don't know what triggers test gathering. PSS: In each test binary at least one QTest::qExec should be expanded out of MACRO. From this point - AutoTest shows also test runners hidden in MACRO and run then all.

@Akzmn Note that if you use setPixelSize() method, for the same size font, on higher resolution screen (higher density of pixels and hence smaller pixel size), it will appear smaller. Is this what you want? Or you want it appear physically the same size on screens with different resolutions?

Hi Only MainWindow can have a ToolBar in designer. However, you can add one from code but not all features work when its a widget it lives in. https://stackoverflow.com/questions/38392322/how-to-create-qtoolbar-in-qwidget

yes, WMP can play h.264 files, but i'm not convinced that is a fair test, because WMP is quite savvy about choosing what back end to use to play the media you throw at it. Qt, on the other hand, is not.

Hi jsulm, Thanks for your guidance.I successfully integrated the svn in SubVersion.

please look at this thread about Application can't start because could not find or load Qt

I tried to investigate the issue further and figured out the following: it seems to be a problem with gdb and its disassembler when I start gdb in the console, it doesn't show me where the crash occurs, too in the debugger log, I get an error message "Disassembler failed" I tried also on another VM (Win 10, also) and a Win 7 Desktop and it works on the VM, however not on the Desktop and my first VM. I have no clue what the differences between these installations are :-( Is anyone aware of any Windows/Qt/MinGW settings that could make the disassembler fail? Thanks for any ideas, Sebastian

Hi There is also UNAME = $$system(python /home/master/test.py ) message( it says: ($$UNAME) ) http://doc.qt.io/qt-5/qmake-function-reference.html [image: sH1AD4.png]

Replace 1 by true

@SGaist QxOrm seem to be the right direction. I will check it out I would like then to have a tool which superordinates scxml and QxOrm. That could reduce textual coding to an absolute limit

Probably the QT_PLUGIN_PATH setting is needed for Anaconda3 to run, but it needs to be removed for the other guys to be healthy. So, what you can do is to remove the QT_PLUGIN_PATH, open a CMD window and type control sysdm.cpl Then select the 3rd tab *Advanced" and click on the 4th (lowest) button (should be named "Environment variables" or something similar) Another dialog box opens which will allow you to remove QT_PLUGIN_PATH. Then if you want to run Anaconda 3, you can open a CMD window and type set QT_PLUGIN_PATH=c:\Anaconda3\Library\plugins\ and then start Anaconda 3 from that CMD window. That way the setting will affect only that CMD window and not the other Qt guys :-)

So it doesn't work even with developer-build :/, so recompile myself didn't help, still any solution.

It is possible. As a user programmer (for many years) I have never had the need to write my own debug helpers. You should try asking in the mailing list, where you may attract the attention of Qt's developers (they don't frequent the forum).

You can try to use the inheaderfile keyword.