Qt 6

@Croitor-Alexandru
not it's not a problem,i have solved it ,that is because i deploy it with dos mode under windows,so issues showed up ,i have to do this under dos of mingw64 Qt6.24,now it's ok,anyway thanks a lot

best reguards

Sam

@nicker-player said in How to defined the MACRO CODE for the slots functions?:

I dont want to write so many the same codes.

What exactly do you think you're saving here? I would guess the time discussing here is already much more than you're saving.

Hi friends,

I also encountered this issue and solved it in a rather strange way.

I have Qt Creator 7.0.2 based on Qt 6.2.3.
I have installed two development Kits:

Qt 5.15.2 MSVC 2019 64bits Qt 6.2.4 MSVC 2019 64bits

When I create a new QtQuick project with Qt 5.15.2 as main Kit my code is similar to you @L_A_Reeves :

import QtQuick 2.15 import QtQuick.Window 2.15 Window { width: 640 height: 480 visible: true title: qsTr("Hello Canary") }

If I switch to the Design View, then I see the infamous bug :
2022-07-15 15_25_26-main.qml @ Canary - Qt Creator.png

But, If I add the build Kit Qt 6.2.4 to the project, select it and then switch to the Design View, here I can see my Window:
2022-07-15 15_27_08-main.qml @ Canary - Qt Creator.png

So my first conclusion is that, depending on the version of Qt used by your Qt Creator, you need to have the equivalent Kit selected
so that the Design View can interpret correctly your QML.
If you have Qt Creator based on Qt 6.x then I believe you need for your project to select a Qt Kit 6.x to be able to see your interface in the Design view.

That's my first conclusion. Hope it helps somebody.

Hi,

As you already found out, that part is specific to the Android platform. Qt does not embed the JVM in any case. Those are just Qt wrapper on top of the standard JNI functionalities.

Qt has otherwise nothing specific for Java. There is the Qt Jambi project that provides bindings for Qt for the Java language.

@SGaist yeah regular users of TRSE either use x86_64 on macos or build themselves. None of the nightlies are arm-based - for now

Hi and welcome to devnet,

Please provide a minimal compilable example that shows that issue.

You should also check the bug report system. If memory serves well, there has been some issues related to stylesheets.

@kkoehne Great, thanks, yes "-nomake tests" solved my problem. As for tests, I will build them for the required module myself.

It worked like this.
Thank you all for your precious help.

void SecDialog::on_pushButton_clicked() { hide(); MainWindow *mainWindow = new MainWindow(); mainWindow->show(); }

@jsulm It worked. Thank you so much.

HEllo All
YEs, just kidding, i know i always can't wait.
So yes, i close and solve this topic.
Should be a topic itself
Regards!
B.HAHN

Thank You (I am a noob in Qt)

@Phil7789 said in Set up additional include paths and library paths:

include_target_directories

it's target_include_directories(), also please try with forward slashes

Are shlwapi.lib; user32.lib; Ws2_32.lib; automatically included in Qt or do I have to specify the full path for them too (I assume they're all system32 libs)?

Not by Qt, but the default linker search path.

Thank you, now I got why actually mostly pointers are used.

@JonB Thank you so much :D

@nicker-player
This is not legal C++ code. The @ s are obviously intended so that something pre-processes this to change the @...@s. But nobody can tell you where/what that since you say nothing about where this is, or whether it has anything to do with Qt....