@lorn-potter said in WebAssembly for Qt Creator: @tansgumus For Qt 5.15, you need emscripten 1.39.8, you have 1.38.8 Sorry I sent the wrong log, below the right one. $ em++ --version emcc (Emscripten gcc/clang-like replacement) 1.39.8 (commit 6b0d151917fe508007d9d76791369ec94c4eb304) Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt) This is free and open source software under the MIT license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ echo $PATH /home/tansu/.emsdk:/home/tansu/.emsdk/fastcomp/emscripten:/home/tansu/.emsdk/node/12.9.1_64bit/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin $ emcc -v emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 1.39.8 clang version 6.0.1 (/b/s/w/ir/cache/git/chromium.googlesource.com-external-github.com-emscripten--core-emscripten--fastcomp--clang 98df4be387dde3e3918fa5bbb5fc43e1a0e1daac) (/b/s/w/ir/cache/git/chromium.googlesource.com-external-github.com-emscripten--core-emscripten--fastcomp b4837f88af2d240abb550c0bbd47f3b8ffe5985a) (emscripten 1.38.31 : 1.38.31) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /home/tansu/.emsdk/fastcomp/fastcomp/bin Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/8 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.5.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.5.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8 Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.5.0 Candidate multilib: .;@m64 Selected multilib: .;@m64 shared:INFO: (Emscripten: Running sanity checks)

Hi and welcome to the forums. Go to the forms folder and click UI file or go to Widget.cpp and see if it has UI The reason the Design is disabled is that you are in main.cpp and it has no design file. So a Widget does not have to have a visual UI file. its optional. And its ok to mix both UI file and code. or just create GUI from code only. But starting out with Qt, its good to use UI files so its easier to inspect the widgets etc. Also, use shift + f4 to switch between Designer and the code. Pressing the buttons Edit / Design does not work as one would expect and show you the UI files as XML and tell you cant edit it.

@ted-dr HI I hope developers would remove this feature or make it optional at least. This would become problematic with standard structured folders across multiple IDEs. Feel free to open an enhancement ticket and post link here. People can then vote for it, if they like you - feel the good old way was the best and if enough votes then it might happen :)

Are running this on two different computers (or VMs)? It seems there are more variables involved than just 'different version of QtCreator'. Working: Qt 5.12.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.3.0) on "xcb" OS: Ubuntu 19.04 [linux version 5.0.0-38-generic] Environment: QT_ACCESSIBILITY="1" QT_AUTO_SCREEN_SCALE_FACTOR="0" Not Working (note, QT_ACCESSIBILITY is not set): Qt 5.12.4 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.2.1 20191008) on "xcb" OS: Ubuntu 19.10 [linux version 5.3.0-40-generic] Environment: QT_AUTO_SCREEN_SCALE_FACTOR="0" Do you have additional KDE packages (not sure what that the 'kdedev' folder is) installed on the one that's working? Does your application depend on them? Can you run it in debugging to see where exactly it is crashing?

Hello @mcleary Thank you for your response It really cleared up things to me I am gonna check the directories, but, the way you explained makes a lot o sense to me. It saved a lot o time. Regards

@SGaist Thank you.

Hi How did you install Qt ? When using the online installer you can choose the install dir. Did you try locate libqxcb.so to see if its somewhere else? Also just to be clear. This errors come when running via Creator ? Not trying to run .exe alone. Correct ?

@aha_1980 Here's how I bootstrapped new working settings for QtCreator. On Windows the settings reside in <user>\Appdata\Roaming\QtProject, which contains files QtCreator.db, QtCreator.ini and directory qtcreator with lots of subdirectories, xml files etc. Renaming that directory then running QtCreator created a new settings directory (from a template kept in the Qt distro) . After that, QtCreator started behaving normally, though of course without any memory of previous projects or kit associations. Copying the QtCreator.ini file from the renamed directory restored those memories but did not make the bad behavior come back. Apparently the root problem is an incompatibility between Qt Creator 4.10.2 and some old file in the settings folder. In my case those files were created years ago by QtCreator 3.5. And since 3.5 does not even support VC 2015, I guess it was high time for a change.

@Exotic_Devel said in Qt Creator external tools paths: What about the problem with qmlviewer, can you give me any suggestions? I honestly have no idea what that is. Looking in the qmlviewer.xml file, it seems to be related to Qt Quick 1, so likely a Qt 4 remnant. Regards

A library is not an application. If you are targeting several Linux distributions, the nicest would be to provide a package using their format e.g. .deb files for Debian based distributions. As for Windows, there's no real package format. Maybe using something like conan.io might be an option. Otherwise an archive that provides your .dll, header and .lib files for the various compilers you want to support is usually good enough. However packing a full version of all your dependencies, while it sounds nice, might prove problematic. If you provide them, then you should also take care of updating them in case of security issues found during the year.

Hi, I think you are looking for QMAKE_RPATHDIR.

@mrjj Excellent! setMinimumSectionSize did the trick. setRowHeight does not seem necessary.

Hi, try: myWidget->setGeometry(secondScreenGeometry);

@Hitokage OK looks like the new lupdate version needs additional info about the file's language so I had to add something like this: <TS version="2.1" language="cs_CZ"> Works now!

@fcarney I can't beleive I missed your question. Comparing with Heob, Deleaker provides more features like taking snapshot at any moment, and comparing them later. Besides heap allocations, Deleaker also tracks COM/ActiveX/GDI/USER32 leaks etc.

Just an update. It looks like the QtCreatorDeployment.txt file is only taken into account by CMake Project or Generic Project. So I created a Generic Project, add the Python file(s) to the .files file, removed all the steps from the Build Settings tab, and configured the Run Settings with a Custom Executable where I set python as the remote executable, and main.py as the command line arguments while enabling Forward to local display. And it worked :-)

@aha_1980, @Buckwheat Thank you very much! This is very helpful. Don't worry, this code has been in production for twenty-five (25) years, and has run on hundreds of thousands of desktops. It was first written with compilers that didn't have 'const'! We'll deal with it when we have a program that runs. It's all good :o)

And just to add to @mrjj, no Makefiles. These kind of files should only exist in the build folder. If you have a duplicate in the project folder, it will drive you crazy.

Hi @MrRobot, Glad you figured it out. So please mark this topic as SOLVED now. Thanks! PS: If you want to move a topic later, just ask a moderator to do so (if you can't do yourself).

Hi and welcome to devnet, That's a question better asked to the Qt Company directly and/or to a lawyer.

hmmm Common mistake. Qt Creator is not Qt. Now you can move the case to SOLVED.

@sierdzio Thank you. I am following the most-recently-updated instructions from here I tried removing exclusion of qt gui but my error persists

Code wise using: QGroupBox *groupBox = new QGroupBox(tr("My Group Box")); QGridLayout *layout = new QGridLayout(groupBox); layout->addWidget(new QPushButton(tr("My Nice Button")), 0, 0); layout->setColumnStretch(0, 1); layout->setColumnStretch(1, 1); does what you want.

@Kinesis You should delete them when they are not needed anymore

@jsulm got it got it . Thanks .

You might have modified PATH in your terminal session only for example. Or you may have modified PATH in the Run part of the Project panel.

I know this answer is a bit late, but one solution that comes to my mind is to separate UI from logic. Create one file (e.g. a ui.qml file) for your UI and use it in another qml file.

Sounds rather like a job for libusb

@Sergey-I. said in Wrong char type detection in debugger: Has anyone reported this to the bug tracker? I don't know. Did you check that?

@Calvin-Richerd On OS I'm familiar with, the OS's notion of "fullscreen" means "full screen" and not "full desktop". However you can fudge a multi-window full-desktop window by digging into desktop geometry via http://doc.qt.io/qt-5/qdesktopwidget.html and creating a sufficiently large borderless window. Not sure how things work these days but it used to be that even if the screens had their own GPUs, all of an application's rendering would be done by one screen's GPU, and then that would be copied to the other screens. If performance is important it maybe better to create a multi-window application with a window on each screen. Couple of ways of doing this: a. Render the window to some offscreen framebuffer, then do 2 copies of the rectangles on either side of the wrap line to the appropriate parts of the actual screen. ie if your framebuffer contains [ABCDEF] but it's rotated 2 characters then you'd copy [CDEF] to the left of the screen and [AB] to the right to get [CDEFAB]. b. Create an application which actually has content [ABCDEFABCDEF] and then just display the right subregion so it looks like its wrapped if you display [CDEFAB]. If the user goes off one end or the other just completely jump to the other end. Not sure how applicable these ideas are to QML apps though. You can do quite a bit of messing with rendering using ShaderEffect, but that doesn't help route mouse events to the right place in a displaced "underlying" layout.