Qt Creator and other tools

At first thank you for your help sierdzio. ^_^ Split project files in different part didn't like so much than, unfortunately, it seem the only way available is to execute manually my task before compilation phase as you suggested...

I have all files of the project locally, so I can build it. But only those files I have "checked out" in my source code control are write-enabled (lack the read-only flag). While I'm already working on those files, I would like to correct certain things using find and replace.

If I leave the field empty and click to accept, the translation remains as untranslated and it prints the default text. In my previous example, if I leave its field empty I get "ñ". Regarding the option of changing manually the .ts file, I would prefer not doing so if there's an easier and faster way. If not, I'll do it. Thanks sierdzio!

@SGaist said in Creator: How to dismiss semantic warning?: Hi, I'm not aware of such a feature. I'd recommend asking this on the Qt Creator mailing list. Well, I had to turn off Clang code model anyway, because it tends to lock files while they are being handled by the source code control (see https://bugreports.qt.io/browse/QTCREATORBUG-15929). I'll rely on static code analysis to reveal such semantic errors - and there I know how to make exceptions.

@maydin As libs are not located in include directories it should be: LIBS += -L/usr/lib -lncurses

Hi, the issue was caused by an wrong checksum inside the package. We have uploaded a new beta version to the downloads page some minutes ago, though it might be visible first after short synchronization period. Link -- Karsten

@jzinqt Super. That is often easier as it comes complete with compiler and debugger. Qt for Visual Studio does not as its not permitted.

@jsulm Yes

Well, I'm not sure commenting it will cause some side effects, it seems that LD_LIBRARY_PATH in the qtcreator.sh affects the system one.

Hi, Can you share the thread where you find that ? If you want such a status report, you should rather check the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

@SGaist : Ubuntu might provide that, but Debian doesn't. But no matter, because I have the server up and running. Now I just have to figure out why my GUI client doesn't connect even though the CLI client does.

@DocDJ said in How can I send output to a widget: @mostefa THANK YOU, THANK YOU!!! That did it. I will analyze it to understand what I did wrong. So the problem is solved now? Good ! I advice you to read more about qt , if you want to go further http://doc.qt.io/qt-5/gettingstarted.html

I checked the source and it seems that my Qt libraries are compiled without qml debug option enabled if (!QQmlEnginePrivate::qml_debugging_enabled) { qWarning() << QString(QLatin1String( "QML Debugger: Ignoring \"-qmljsdebugger=%1\". " "Debugging has not been enabled.")).arg( appD->qmljsDebugArgumentsString()); return; }

@fabi_ said in Designer: "Qt Quick emulation layer crashed" on OpenSUSE: The link just takes me to line 1 of the qml file and this happens on any project (examples as well as a freshly created project with no changes). I'm running a fresh install from the unified linux installer in my home directory on OpenSUSE: After re-reading your post, that line makes me think even more you are accidentally mixing Qt libs. It's very common. You can try ldd on your qt creator and see what it shows. Not guaranteed to catch it but should give you an idea. Another thing try launching your designer/creator with an LD_LIBRARY_PATH that points to your custom installed Qt. And finally, you could try restricting access to the system Qt libs (this could affect your apps though if you're using KDE or Qt based apps).. I do a chmod 000 <qtstuff> when I want to narrow things down like this, then restore the permissions when I'm done.

Hi and welcome to devnet, You can check the bug report system and open a bug report against the Qt Creator project for that. Even better, if you know where the missing documentation should, you could consider providing a patch for Qt Creator's sources.

Cool, thanks.

Great ! Then please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)

@SebastianM Ah yea you'll have to wait for someone else to help then. I don't use Qt Creator so I can't really help with build targets there. You could always run your builds manually on the command line. I do that most of the time I'm working anyway since I always have a terminal open. But if you want Creator integration that's out of my league, I've barely ever launched it and have been writing Qt code for like 14 years or so.