General and Desktop

I would suggest following the cmake getting started guide. There are some hints to simplify the content of your CMakeLists.txt file. One of which is to not include the headers in the file list you pass to qt_add_executable.

If you want to sort, why are you setSortIndicatorShown(false); ?

I don't understand your problem - what exactly is wrong here?

@Pl45m4 i do that,and also dosen`t work.

@JacobNovitsky Actually you can when compiling QtCreator from source and modifying that bit of code. I don't know if the community license allows that Funny enough I've been talking with one of the QtCreator maintainers on the Qt Discord about that exact menu bar lately, because I was interested in how it's set up and done. I might want to use something similar in one of my personal projects (also VSCode has some sort of side menu bar where you select between run, extensions or file system view, for example)

@ctrkalk Then I know the reason, it is not that it doesn't show, but the stylesheet doesn't work, so the widget is totally transparent. There're already quite a lot posts in the forum asking about subclassed QWidget's stylesheet not working. It is also documented: If you subclass from QWidget, you need to provide a paintEvent for your custom QWidget as below: ... But this is the first time I know that a subclassed QWidget without Q_OBJECT would have stylesheet working :) BTW, the simplest solution for this kind of problem (if you don't want to reimplement paintEvent) is to subclass QFrame instead of QWidget, or using palette instead of stylesheet.

@AndyBrice said in Qt 6.10 and text encodings: @cristian-adam I used to build Qt myself, many years ago. But it just got too difficult. Is ICU going to supported in a future Mac binary release? No idea. I've opened up https://bugreports.qt.io/browse/QTBUG-141087

Hi, Another option is to create a QProxyStyle to do the painting you want.

this Bash solution didn't work for me, on account of a multi-level project structure that i was dealing with. (at least, i think it was multi-level.) What did work for me was something akin to the following: qmake ./my_project.pro -spec linux-clang CONFIG+=release CONFIG+=DISABLE_DEVELOPER_MODULES CONFIG+=force_debug_info && /usr/bin/make qmake_all make -j $CORES VERBOSE=y all &>make_output.txt compiledb --parse make_output.txt mkdir build/yamls run-clang-tidy -p . -j $CORES -clang-tidy-binary $CLANG_TIDY_PATH -checks=-*,bugprone-*,clang-*,cppcoreguidelines-*,modernize-* -export-fixes build/yamls this gives me a bunch of moc_* complaints, but also complaints on my actual code. the moc_* complaints seem to be clang-tidy's complaints about Qt itself, so i filter those out.

For reference The debug pdb files available for Qt 6.9.1 and 6.10 WERE INSTALLED and I NEVER REFUSED to install them e.g. qwindowsd.pdb is there next to qwindowsd.dll

Hi, The pre-built Qt 6 for macOS is multi-arch.

@sairun said in QSqlQuery prepared statment using QString as a bind value: somewhow it doesn't get replaced as a regular string in the query. This would completely contradict the prepared query idiom... https://en.wikipedia.org/wiki/Prepared_statement

@daviddev You have a Windows "UI" program, i.e. linked as a "windows" rather than a "console" application. I think you will find: when a Windows UI application is launched, whether from a terminal or icon-shortcut, that stdout and stderr are attached to "nowhere", so anything written to them "disappears". If it works from FrontEnd.exe > output.txt that implies that the calling shell has redirected stdout to the file so it stays like that when it runs and you get output there. The stuff inside Creator with/without terminal is special code in Creator so that's different. I am not sure what exactly you want to achieve for what situation(s). Logging to file sounds like a better option than stdout/err for a UI program anyway. Under Windows you might also try downloading something like dbwin, dbwin32 or whatever the modern replacement is and running that --- that displays any text sent via Win OutputDebugString(), it may also capture some other stuff I'm not sure. Your program can also call Win32 AllocConsole() to allocate a visible console window (like a terminal) and that will have stdout/err attached, instead of your attempted "supporting QProcess". Finally a UI program could create e.g. a permanently visible modeless dialog/window with, say, a QPlainTextEdit in it to which you send all your output messages for it to display.

here is the thread backtrace: Process 2636 stopped * thread #18, name = 'QSGRenderThread', stop reason = EXC_BREAKPOINT (code=1, subcode=0x19ea5a3ec) frame #0: 0x000000019ea5a3ec libsystem_c.dylib`__abort + 160 libsystem_c.dylib`__abort: -> 0x19ea5a3ec <+160>: brk #0x1 libsystem_c.dylib`abort_report_np: 0x19ea5a3f0 <+0>: pacibsp 0x19ea5a3f4 <+4>: sub sp, sp, #0x30 0x19ea5a3f8 <+8>: stp x20, x19, [sp, #0x10] (lldb) bt * thread #18, name = 'QSGRenderThread', stop reason = EXC_BREAKPOINT (code=1, subcode=0x19ea5a3ec) * frame #0: 0x000000019ea5a3ec libsystem_c.dylib`__abort + 160 frame #1: 0x000000019ea5a34c libsystem_c.dylib`abort + 180 frame #2: 0x0000000103b9c060 libclang_rt.asan_osx_dynamic.dylib`__sanitizer::Abort() + 68 frame #3: 0x0000000103b9b728 libclang_rt.asan_osx_dynamic.dylib`__sanitizer::Die() + 212 frame #4: 0x0000000103b9b7d0 libclang_rt.asan_osx_dynamic.dylib`__sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) + 156 frame #5: 0x0000000103b9c190 libclang_rt.asan_osx_dynamic.dylib`__sanitizer::UnsetAlternateSignalStack() + 100 frame #6: 0x0000000103b86a8c libclang_rt.asan_osx_dynamic.dylib`__asan::AsanThread::Destroy() + 252 frame #7: 0x000000019eb1db88 libsystem_pthread.dylib`_pthread_tsd_cleanup + 448 frame #8: 0x000000019eb20968 libsystem_pthread.dylib`_pthread_exit + 84 frame #9: 0x000000019eb20278 libsystem_pthread.dylib`_pthread_start + 160

@Bonnie Thanks a lot! Required some tweaking but this solution worked. Works on both Mac Intel and Silicon. Added the switch to my main() with an if-statemet as I want it to affect all my dialogs when on a Mac. #if defined(Q_OS_MACOS) QApplication::setAttribute(Qt::AA_DontUseNativeDialogs, true); #endif Then in my editor file: static const QString kFilters = "C/C++/CS Files (*.c *.cpp *.cc *.cxx *.cs *.h *.hpp *.hh *.hxx);;" "Pascal Files (*.pas *.pp);;" "Python Files (*.py);;" "Ada Files (*.ada *.adb *.ads);;" "Qt Project Files (*.pro);;" "Text and Markup Files (*.txt *.json *.xml *.md);;" "All Files (*.*)"; QString fileName; #if defined(Q_OS_MACOS) // non-native dialog QFileDialog dlg(this); dlg.setWindowTitle(tr("Open File")); dlg.setFileMode(QFileDialog::ExistingFile); dlg.setViewMode(QFileDialog::Detail); dlg.setDirectory(QFileInfo(startDir).isDir() ? startDir : QFileInfo(startDir).absolutePath()); dlg.setNameFilters(kFilters.split(";;")); dlg.selectNameFilter("C/C++/CS Files (*.c *.cpp *.cc *.cxx *.cs *.h *.hpp *.hh *.hxx)"); // dlg.setOption(QFileDialog::DontUseNativeDialog, true); // if not set in main() if (dlg.exec() == QDialog::Accepted && !dlg.selectedFiles().isEmpty()) fileName = dlg.selectedFiles().constFirst(); #else fileName = QFileDialog::getOpenFileName(this, tr("Open File"), startDir, kFilters); #endif if (!fileName.isEmpty()) { openFile(fileName); }