General and Desktop

@JonB hi sure here it is: link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='' processorArchitecture=''" /MANIFEST:embed /OUT:debug\tester.exe @C:\Users\server\AppData\Local\Temp\tester.exe.612.0.jom LINK : fatal error LNK1104: cannot open file 'C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib.obj' "C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32" is where i installed qt compiled from source. again the issue is that qmake is automatically adding C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib to the LIBS variable when generating the makefile but this is clearly a PATH not a library. The linker is therefore looking for lib.obj library which obviously does not exist here's the relevant section in the makefile: LIBS = C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib\Qt5Widgetsd.lib C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib\Qt5Guid.lib C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib\Qt5Cored.lib glu32.lib opengl32.lib gdi32.lib user32.lib C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib\qtmaind.lib C:\Qt\qt-5.15.8-dynamic-msvc2019-x86_32\lib shell32.lib

Oh... I figure it out. I think it's the problem of not using the pointer references. // QsciAPIs api(this); // crashes! QsciAPIs* api; api = new QsciAPIs(this); // Now it won't crash for (const QString &s : /**/) { ///... ///... ///...

If you're okay with disabling the animation part of the drop down, it will prevent the black box from appearing. You do this through QApplication::setEffectEnabled: QApplication::setEffectEnabled(Qt::UI_AnimateCombo, false);

@xiaoyingwang hi, it might be doable but it's not guaranteed to work on all platforms. See this Stack Overflow thread.

@Christian-Ehrlicher said in More MySql issues.: @Chrisw01 said in More MySql issues.: They have also been placed within the lib files of the compiler as well. Why? What should this help? I don't know where you put them, the important thing is that the libmysql.dll is found when the application is run - so adjust your PATH accordingly. And don't mix MSVC and MinGW libs & plugins. Honestly, I have been fighting this problem all week. Reading blog after blog after blog. I did not mix up the libraries. I followed MSVC instructions for MSVC and MinGW instructions for it. The problem appears to be where to place the libmysql.dll file so it can be seen within Qt Creator while I Develop. I know it needs to be in the application folder when you distribute. Previously placing the libmysql.dll file within the applications build folder satisfied this apparently not anymore. I managed to find a fix however. I added created a folder and placed the required files there. Then I added LIBS += -L"C:\MySql" -lmysql to my project file and the program now works. May or may not be the proper way to do it but it works. I have not had to do this in the past but again, I've taken a break from Qt for a while and things may have changed. Thanks for your help..

@Lonsdaleite I created my own info.plist instead of copied the file generated with the xcode package for iOS and it solved the problem. Don't know why, but it works ! Thanks for you response. Little question for the end : i created an icon catalog assets which include both iOS and macOS Icon (required for iOS if i understand all ?). Can i use it for Mac bundle instead of .icns ?

@JoeCFD I added: printer->setPageOrientation(QPageLayout::Portrait); And now it prints in Landscape!!! So no, did not help...

@Christian-Ehrlicher https://doc.qt.io/qt-6/qobject.html#qobject_cast Thanks. This is an excellent hint. There are indeed some qobject_cast in our code, in close vicinity to the classes that did not suffer Q_OBJECT to be removed.

@Perdrix said in Using translatable strings in a static library: How should I modify that to also load the ts files starting with "kernel"? The same way - there is no difference, the only thing you have to do for static app is, as the doc says and you do - init the resources with Q_INIT_RESOURCE

@ChrisW67 I dont get warnings, but plenty errors. It seems that the editor clang plugin does not recognize the qt library

@Dragoon yes... it was... using a precompiled QtCreator binary found here the plugin works. Nope it was not... the problem was the path of plugins directory. As QtCreator config file states the folder in which it search for plugins is the plugins\bin\designer subfolder of the QtCreator tool directory i.e. (in standard Windows installs): C:\Qt\Tools\QtCreator\bin\plugins\designer And not (as make install script like to think): C:\Qt\<release>\<toolchain>\plugins\designer BTW on Windows the plugin must be compiled as Release otherwise QtCreator will not load it but you will have an explanation on the: Tools->Form Editor->About Qt Designer Plugins dialog.

@jorTry85 said in C2102: '&' requires I-Value: When i now try to comile it in QT Qt is not a compiler. You seem to be using MSVC compiler. That is where you you should be looking. I suggest you Google for C2102 and read e.g. the stackoverflow posts. It looks like you either change the compiler options ("disabling /permissive-") or better actually "fix". I believe it is telling you that those functions return a "temporary" object, so you shouldn't take its address, you should rather assign to a local variable and use that, or pass a const reference?

I was looking for bool MyBaseClass::event(QEvent* e) { if (e->type() == QEvent::DynamicPropertyChange && qobject_cast<QDockWidget*>(parent())) //... }

@SGaist, I faced the same problem on Ubuntu 20.04. I have Qt5 and Qt6 installed, in both versions toolTips are not displayed. However, in Windows 10 everything works without problems. Windows 10: [image: 1e3bfadc-2a1a-475d-be1a-dc214a2a252a.png] Ubuntu 20.04 [image: d589b262-f452-4fd5-9e36-6a55b7d550e4.png]

@agmar C++ basics. What you wrote is not valid C++. A style-sheet is a string... And you also need to use https://doc.qt.io/qt-6/qwidget.html#styleSheet-prop if you want to set style-sheet in code.

@masa4 said in Proper way for adding 2nd language: But how will i change dynamically created widget's texts like this messagebox? Since you can't show a MessageBox and change the language simulatneously this shouldn't be a problem since the next time you call the message box you text is properly translated due to the tr() call. If you changed a text in your ui after setupUi() you have to do the same manually after the language change event. See the documentation.

@wuj10n When adding QListWidgetItem to QListWidget, update QListWidgetItem flag like this listeWidgetItem.setFlags(listWidgetItem.flags() & (~Qt.ItemIsSelectable))

@Christian-Ehrlicher forget it I was editing the reply...